We are migrating our .NET 1.1 applications to .NET 2.0. With one exception this went smoothly. But we reference a COM object (writtien in VS6 C++) which isn't strongly named. The application compiles and runs in VS2003, but whe we try to compile it in VS2005 (after conversion) we get a message indicating that the COM object is not strongly named.
Can anyone point me to information on how to strongly name a COM object
Thanks.
How to make a COM object strongly named.
O.Tacke
COM objects are normally written in unmanaged code and therefore are not strongly named as they aren't assemblies. However in order to use a COM object you normally import the COM object into your project or use tlbimp. In both cases a proxy assembly is created that your .NET program actually talks to. If your program is strongly named then all its referenced assemblies (including the proxy) must be strongly named. Tlbimp exposes some command-line arguments to permit you to generate a strongly named proxy assembly that you can then use in your strongly named program. I don't believe VS gives you the option of strongly naming a COM proxy assembly when you import it via VS. Therefore you'll need to generate the proxy through tlbimp and then reference the generated assembly in your project. Note that provided the COM object doesn't change you only need to import it once.
Michael Taylor - 6/19/06