O
Oleg Ogurok
Hi all,
I have a C# class library project that needs to be registered for COM
interoperability. I set the "Register for COM Interop" to true in the
project's properties. When compiled, VS.NET creates a .tlb file under
obj/Release or obj/Debug, depending on the current configuration.
I also have a deployment project that uses the "Primary Ouput" of the class
library. The problem is that every time I launch VS.NET and try to build the
deployment project, VS.NET keeps trying to put both .dll and .tlb into GAC,
and then complains that only assemblies can be placed in GAC (makes sense).
I then create a folder under Common Files and move .tlb there. This builds
fine,
and I check the project back into SourceSafe.
However, the next time I launch VS.NET and try to build, the problem comes
back.
Is there any better way to deploy my class library for COM interop?
Thanks,
-Oleg.
I have a C# class library project that needs to be registered for COM
interoperability. I set the "Register for COM Interop" to true in the
project's properties. When compiled, VS.NET creates a .tlb file under
obj/Release or obj/Debug, depending on the current configuration.
I also have a deployment project that uses the "Primary Ouput" of the class
library. The problem is that every time I launch VS.NET and try to build the
deployment project, VS.NET keeps trying to put both .dll and .tlb into GAC,
and then complains that only assemblies can be placed in GAC (makes sense).
I then create a folder under Common Files and move .tlb there. This builds
fine,
and I check the project back into SourceSafe.
However, the next time I launch VS.NET and try to build, the problem comes
back.
Is there any better way to deploy my class library for COM interop?
Thanks,
-Oleg.