Signing problem

A

Ayende Rahien

I'm trying to build my application with a strong name, but I get this
errors:
error CS1577: Assembly generation failed -- Referenced assembly
'AxInterop.SHDocVw' does not have a strong name

error CS1577: Assembly generation failed -- Referenced assembly
'SgmlReaderDll' does not have a strong name

I've no control over either one of them, how do I get this, or do I've to
resign myself to no strong names?
 
J

Jan Tielens

If one of your assemblies in signed, all of the other assemblies that you
use should be singed too. So I think the only solution is to sign the other
assemblies as well (if that is possible).


--
Greetz

Jan Tielens
________________________________
Read my weblog: http://weblogs.asp.net/jan
 
J

Jan Tielens

So this is an ActiveX component. You should check out the article I
mentioned in my previous post. You don't need to sign the ActiveX component,
but you should sign the Interop assembly that is generated by Visual Studio
..NET (when you added a reference to a com component).


--
Greetz

Jan Tielens
________________________________
Read my weblog: http://weblogs.asp.net/jan
 
S

Slava ilyin

Don't know whether it is a good solution, but I'm using it for a long
time without any problems.

So, you have some COM (ActiveX object) and you wants to sign Interop
of this COM object:

You must sign your Interop.YOURLIB reference with the Assembly key
1 Run tlbimp.exe YOURLIB.DLL /out:Interop.YOURLIB.dll
/keyfile:YOURKEY.snk
where "YOURLIB.DLL" is your source ActiveX component (you can simple
find path to it when add reference to the project).

2. Now you can add Interop.YURLIB reference into your project (remove
old previoisly) and build it.
 

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

Top