...is not strongly named...

T

Tamir Khason

I have a form. On form there is my control (all of control's assemblies
signed by strong key), BUT while running I recieve
he located assembly 'MyFooAssembly' is not strongly named.

While looking into References node in project the assembly 'MyFooAssembly'
is strong key = true. So what cna be a ptoblem???



TNX
 
B

Bonj

Make sure that all its dependencies are also strongly named. Due to a rule
of strong named assemblies, if any assembly is to be strongly named, all its
dependencies must also be strongly named.
 
T

Tamir Khason

I solved this problem. The VERY strange issue
All dependancies WERE strong named, BUT in manifest of the class library
there were not tokens... How can it be?
 
T

Tamir Khason

Public Token of referenced assemblies is added to current assemblie's
manifest section when the referenced assemblies are strong named. This way
FW knows that assemblies referenced are original and not changed/
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Can strongly named assembly1 reference non-strongly named assembly2 ? 5
Anybody use Strong Name Signing? 7
Strong name assemblies patching problem 5
Debugging - Public key , Delay signed , Strongly Named assemblies 0
Strongly named assembly won't load 1
problem with assembly signing and strong names 1
Interop.MSHelpServices not strongly named 1
Assembly not strongly named problem need help 3

Top