Strong Names

[Scott Meddows]

I have a major problem.

I have a deadline of Monday and I don't know if I can do what I need to do.
(darn Crystal Reports for not migrating to a different server!)

I'm adding a reference to a COM control in VS. However, my assembly is
signed with a strong name. When I attempt to compile the exe I get the
error of "Unable to emit assembly: Referenced assembly 'Interop.SHDocVw'
does not have a strong name"

Is there a way I can tell the compiler to not check this dll for a strong
name? Is there a way I can have VS generate this proxy WITH a strong name?

Help is needed and appreciated.

Thanks
Scott

 

[Mattias Sjögren]

Scott,

Is there a way I can tell the compiler to not check this dll for a strong
name?
No

Is there a way I can have VS generate this proxy WITH a strong name?

Not when using VB.NET no.

But you can use the TlbImp or AxImp tools to generate the interop
assembly instead. They both have /keyfile options so you can give the
assembly a strong name. Then reference this assembly from VS.NET.



Mattias

 

[Scott Meddows]

I've tried to use that tool and it gives me the error that a CSP cannot be
found for one of the classes in the DLL

What I was trying to wrap is the COM Internet Explorer control.

 

[Mattias Sjögren]

Scott,

I've tried to use that tool and it gives me the error that a CSP cannot be
found for one of the classes in the DLL

Never seen that before. Can you post the exact command line you used
and the error message you got?



Mattias