Can strongly named assembly1 reference non-strongly named assembly2 ?

[Oleg Subachev]

When I try to use strongly named assembly1 that references
non-strongly named assembly2 I get the following error:

"The located assembly '<assembly2 name>' is not strongly named."

How can I force strongly named assembly1 to reference non-strongly named
assembly2 ?

 

[Mattias Sjögren]

How can I force strongly named assembly1 to reference non-strongly named
assembly2 ?

You can't. You can still load the assembly dynamically (Assembly.Load)
at runtime though.



Mattias

 

[Carlos J. Quintero [.NET MVP]]

AFAIK, no, you must sign assembly 2 with sn.exe. For ActiveX controls, see
http://blogs.msdn.com/shawnfa/archive/2005/01/13/352636.aspx

--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
You can code, design and document much faster.
Free resources for add-in developers:
http://www.mztools.com

 

[Guest]

No you can not. But why should you want to? You have an assembly1. And
because you're concerned about security you sign it with a strong name. If
you could reference to an assembly which is not signed. The profit of signing
assembly1 is gone.

 

[Oleg Subachev]

No you can not. But why should you want to? You have an assembly1. And

because you're concerned about security you sign it with a strong name. If
you could reference to an assembly which is not signed. The profit of signing
assembly1 is gone.

The problem arises from the fact that assembly2 is .NET generated COM
Interop
wrapper assembly for Win32 Com server :-(

 

[Mattias Sjögren]

The problem arises from the fact that assembly2 is .NET generated COM
Interop
wrapper assembly for Win32 Com server :-(

You can give those a strong name too, just like any other assembly.
Use Tlbimp with the /keyfile (or /keycontainer) option, or set the
Wrapper Assembly Key File option in the VS project properties dialog.



Mattias