I have a Windows service that I've written in C#. In the business logic, I have a reference to a dll that needs to be registered on the target installation. Currently, it's not being registered on the target machine. On the setup project, I opened the Properties for the dll in question and noticed a 'Register' option that was set to "vsdraDoNotRegister". Should I change this value to "vsdraCOMSelfReg"?
A:
If your DLL is a simple class library DLL in c#, then no you should not try to register the DLL. If your DLL is compiled as a COM library then you should register it.
Brian R. Bondy
2010-06-23 16:37:15
It is a COM library. I actually have the dll set to "vsdrfCOMSelfReg".
jmac
2010-06-23 16:42:52
@jmac: Yes turn the option to `vsdraCOMSelfReg`
Brian R. Bondy
2010-06-23 16:43:58
Originally, I was looking at the Primary Output when I said that it was set to "vsdraDoNotRegister". The COM dll is set to "vsdrfCOMSelfReg". Do I have to change anything on the Interop COM dll?
jmac
2010-06-23 16:56:11
@jmac: I don't think so.
Brian R. Bondy
2010-06-23 16:56:45