Strong Name error building assembly

The Interop assembly the IDE generates for the COM component is not strongly named. You need to generate an Interop assembly with a strong name:

You can use the tlbimp.exe utility to generate a strongly-named Interop assembly from the Foobar dll using a strong name key file you have generated:

From the Visual Studio command line prompt:

tlbimp FooBar.dll /keyfile:FooBar.snk /out:interop.foobar.dll /namespace:foobar

This should create a strongly-named interop assembly which you can reference instead of the one the IDE generates for you. This should get rid of your problem.

Hope this helps

Tom

When I used the tlbimp on the dll it gave me an error saying that it wasn't a valid type library.  I instead used the tlb file.  This appeared to work, but I received several errors all similar to the following


TlbImp warning: At least one of the arguments for '_IOraBindVariable.GetPersistentPointer' can not be marshaled by the runtime marshaler.  Such arguments will therefore be passed as a pointer and may require unsafe code to manipulate.


I am in the process of testing.  Thought I would get your opinion.

I have an ocx that I add as a reference, which creates an interop dll under the obj directory.  No problem up to now because I can run the tlbimp that you suggested.  But when I goto the Customize toolbox and add the same control so that I can drop it on my form, it creates another dll under the obj directory called AxInterop.XXX.dll.  Therfore now I have two Interop dlls created from the same ocx.  One is called AxInterop.xxx.dll and the other is called Interop.xxx.dll.  How do I give both of these a strong name?

Since I have asked multiple question on this thread, I was going to increase the point value, which use to be obvious.  How do you add points to a question now?

Are you still having a problem with this?

Bob

Yes I never received any postings on my follow-up issue

Did this help you?

Bob