We have developed a .NET assembly that needs to be available/visible to both COM (VB6) clients and .NET clients. The assembly is built and seems to be functioning well, but I am not sure what are the best practices and AI methods for deploying that assembly. For now I only need to deploy it within my organization for further testing, but eventually the assembly should be included as part of our main application's installation package.
For example, should I call "gacutil.exe" to register it in the GAC for .NET clients, and call "regasm.exe /tlb /codebase" etc. to ensure that COM clients can "see" the assembly?
Is there a tutorial or how-to that deals specifically with this topic?
Thanks.
FOLLOW US
Get the latest news in Application Packaging