Strong name signing

  • Thread starter Thread starter Michael
  • Start date Start date
M

Michael

Help please

Trying to strong name sign my project within the Assembly using the
KeyFileAttribute with a sn generated key and getting an error message that
one of the referenced dll's (Interop.DAO.dll) is not also strong name
signed. Apparently to sign a project all referenced assemblies supplied by
others must be signed as well.

As such trying to strong name sign the Interop.DAO.dll using tlbimp.exe
with the sn keyfile but now getting an error that says "Interop.DAO is not a
valid type library"

Can anyone please tell me how to strong name sign a reference file in VB2003
if it is not signed by the author (in this case microsoft)

Thanks

Mike
 
As such trying to strong name sign the Interop.DAO.dll using tlbimp.exe
with the sn keyfile but now getting an error that says "Interop.DAO is not a
valid type library"
Click to expand...

You have to point Tlbimp to the original DAO type library, not your
existing Interop.DAO interop assembly.


Mattias
 

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

signing certificate error... 1
strong name 1
Anybody use Strong Name Signing? 7
problem with assembly signing and strong names 1
Strong Names 3
StrongName (sn.exe) works to generate, but fails to return public key! 1
How to get the public key 1
Query in register .Net dll 3

Back
Top