Interop.MSHelpServices not strongly named

[Jack Menendez]

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?
--
Jack Menendez
Redheeler Software LLC

[Eddie de Bear]

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

"Jack Menendez" wrote:

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?
--
Jack Menendez
Redheeler Software LLC