A
Amernauth
Guest
Hello,
I've been using an interop .dll to interface with my COM server successfully but had a question about registration.
Originally I was using a 3rd party installer which registered the COM server during the installation. Now, however, I'm trying to do this myself via the Visual Studio command line and not leverage the installer. I researched the subject on the internet but saw a slew of conflicting answers and not quite sure which one fits my particular case.
I imagine a good test would be to remove the software that the setup installed (but keep the COM server .exe and .tlb files) and then see if I can add my .tlb as a reference in my project again. If unsuccessful then I can try registering the COM server on the command line.
Any help would be greatly appreciated.
Thanks!
Continue reading...
I've been using an interop .dll to interface with my COM server successfully but had a question about registration.
Originally I was using a 3rd party installer which registered the COM server during the installation. Now, however, I'm trying to do this myself via the Visual Studio command line and not leverage the installer. I researched the subject on the internet but saw a slew of conflicting answers and not quite sure which one fits my particular case.
I imagine a good test would be to remove the software that the setup installed (but keep the COM server .exe and .tlb files) and then see if I can add my .tlb as a reference in my project again. If unsuccessful then I can try registering the COM server on the command line.
Any help would be greatly appreciated.
Thanks!
Continue reading...