How to sign a strong name to Interop.SourceSafeTypeLib.dll?

[Guest]

Hello, friends,

I wonder how can I sign Interop.SourceSafeTypeLib.dll a strong name and
reference it from my own dll? (I am using C#.net).

(Interop.SourceSafeTypeLib.dll is automaticall generated when I reference
VSS COM component in my own dll C#.net project)

Thanks.

 

[Nicholas Paldino [.NET/C# MVP]]

Andrew,

Instead of setting a reference to it, use the TLBIMP utility. It will
allow you to point to a strong name which will be applied to the interop
assembly.

Hope this helps.

 

[Sylvain Lafontaine]

I'm not really sure but I think that you cannot: it's part of the security
features of .NET: you must either have access to the full source code of the
library or have its Primary Interoperability Assembly (PIA).

I don't know for VSS but for Office, you can look at the following article
to know how to get and to correctly reference its PIA:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnoxpta/html/odc_oxppias.asp

 

[Chad Myers]

If you can locate the PIA, definitely get that.

However, if you cannot, don't use VS.NET's "Add reference (COM)" feature.

From the cmd-line, use tlbimp.exe. You can specify a key (using the /keyfile
argument).

Once you've generated your interop DLL, reference that from VS.NET.

You'll, of course, need to ship this DLL with the rest of your product.

Also, be prepared/aware that as soon as MSFT releases a PIA for this DLL (if
they ever do, which they may not), that you should switch out your DLL for
their DLL and release a new version of your product.

-c