Strong Name

[Michael Voss]

Hello!

I have to sign my assembly (WinForms C# 1.1) with a string name.
Unfortulately, I'm forced to reference another assembly (no COMInterop
Wrapper) not being signed with a strong name. This results in an compiler
error preventing my assembly from being build. I cannot influence anything
on the creation of the referenced assembly; all I have is a managed dll.

Is there any chance to sign my assembly; if so, how ?

 

[Guest]

The following assumes you are working with a copy of your dll, so if
something goes wrong you still have the original to try again.

You can sign assemblies at the command line using the following tool:

signtool.exe sign /n "Your Company Code Signing" /t
http://timestamp.verisign.com/scripts/timstamp.dll yourlib.dll

Use the VS2005 CMD prompt so it will be in the path. At least, this is how I
do it with .NET 2.0. The previous tools:

signcode -cn "Your Company Code Signing" yourlib.dll -t
http://timestamp.verisign.com/scripts/timstamp.dll

Either way, the timestamp piece is very important. If you don't use the
timestamp, the signing still works. The problems start when the certificate
expires and you didn't use the timestamp, and yes, all certifcates I've
worked with expire.

HTH:
Randy

 

[Michael Voss]

I have to sign my assembly (WinForms C# 1.1) with a string name.

OOOPS! Typo! --------------------------------------------^
Should've been "strong" ;-)

 

[Michael Voss]

Hi !
randy1200 wrote:

[...snip...]

signcode -cn "Your Company Code Signing" yourlib.dll -t
http://timestamp.verisign.com/scripts/timstamp.dll

[...snip...]

Unfortunately, you'd need to use a certificate instead of a .snk-file to use
signcode.exe. I'll have to figure out if my company owns a certificate, but
that's at least one hint.

Thanks a lot!