I've added a weakly named assembly to my VS2005 project (which is strongly named). I'm now getting the error:
"Referenced assembly 'xxxxxxxx' does not have a strong name"
Do I need to sign this 3rd party assembly?
Thanks in advance
Nick
views:
4077answers:
1
+7
A:
To avoid this error you could either
- load the assembly dynamically, or
- sign the 3rd party assembly.
You will find instructions on signing third party assemblies here:
0xA3
2008-12-01 17:26:23
OOO.. I got linked! Cheers :)
OJ
2008-12-08 23:30:20
Thus is signing the assembly an option, I neither wish to load the assembly dynamically nor to sign it. I know that strong naming is in regards of the Global Assembly Cache (GAC). Despite, I don't want to make my assemblies part of the GAC and neither are they COM-visible. I remember partially remember of something we may do that will allow the use of this assembly without signing it. It is somewhere in the options properties or so. Am I out of track wanting to go that way?
Will Marcouiller
2009-09-14 15:34:47
You can use unsigned assemblies if your assembly is also unsigned.
OJ
2009-11-09 12:45:50