Referenced assembly 'Interop.ebCryptLib' does not have a strong name

  • Thread starter Thread starter Alex Ting
  • Start date Start date
A

Alex Ting

Hi Everybody,

I've got this problem when signing this interop. All my project dll's are
signed correctly except for this one where its a com reference.
I've read the KB http://support.microsoft.com/?kbid=313666 but after trying
this it still doesnt work. It either says that it cant find the file in my
bin directory.

Any sugguestions anyone? I've also tried to delete the .snk key and recreate
it and then do the suggested instructions from the KB but to no avail.

Thanks in advance

Alex Ting
 
Alex said:
I've got this problem when signing this interop. All my project dll's
are signed correctly except for this one where its a com reference.
Click to expand...

In the Project Properties window, go to Common Properties | General and
enter the name of your key file in the "Wrapper Assembly Key File"
property. Be sure the key file is in the project folder and not one of
your output folders.

Once that's done, remove the reference to your COM library and add it
back in. VS.NET will sign the Interop assembly upon generation.

--
There are 10 kinds of people. Those who understand binary and those who
don't.

http://code.acadx.com
(Pull the pin to reply)
 
Thanks Heaps!! U DA MAN!

Regards

Ps.. I was also confused what the key was.. I was typing in the Interop name
and all these other weird things.
 
Back
Top