Interop.MSHelpServices not strongly named

G

Guest

I have a forms based plugin architecture using C# that includes help files using MSHelpServices. However, my strongly named assemblies cannot be created because Interop.MSHelpServices is not strongly named. I get the following message during a build, presumedly from AL.exe:

Assembly generation failed -- Referenced assembly 'Interop.MSHelpServices' does not have a strong name

What is the strategy for handling this?
 
G

Guest

Jack,

I'm unfamiliar with MSHelpServices, but I am assuming it's just a COM component. (Because of the 'Interop.MSHelpServices' )

This file (interop assembly) is created for you when you create a reference through visual studio.net, and as such there is no control. However, VS.NET just uses tlbImp.exe which comes as part of the SDK. You can use the /keyfile parameter to specify a strong name key file to use for signing the created interop assembly.

Using this approach to create the interop assembly should help.

Cheers

Eddie de Bear
 

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

Strongly named assembly won't load 1
convert a weakly named assembly to a strongly named 3
Strongly-named assemblies not in GAC 2
problem with assembly signing and strong names 1
? How to strong name a 3rd Party Assembly ? 3
...is not strongly named... 4
Getting Strongly Named Flash Shockwave dlls for use with No-Touch Deployment Smart Client 2
Version Info not showing up in assembly properties for C++ dll 7

Top