I have created a setup project for my application which includes a non .NET
managed code COM object. My COM component is automatically registered when
I build my project.
I'm having problems registering the COM component during installation. In
my setup project, I set the Register property to "vsdrpCOM" for the Primary
Output from the COM project element. But, upon installation my COM
component is not registered.
How do I get my COM component to register during installation?
Thanks in advance,
Mervin Williams
Carlos J. Quintero [MVP] - 13 Oct 2004 16:12 GMT
Using vsdrpCOMSelfRegister should work fine.
If not, some pointers:
1) Try to create a simple setup project sample that registers for COM a
(activex) file (not a project output), to see if it works.
2) Use the proper option of msiexec to create an installation log and
examine its contents to see why is failing.

Signature
Carlos J. Quintero (Visual Developer - .NET MVP)
The MZ-Tools all-in-one add-in, now for .NET: http://www.mztools.com
> I have created a setup project for my application which includes a non .NET
> managed code COM object. My COM component is automatically registered when
[quoted text clipped - 10 lines]
>
> Mervin Williams
???F - 14 Oct 2004 01:51 GMT
Use ShellExecute to run 'regsvr32 ...dll'
> I have created a setup project for my application which includes a non .NET
> managed code COM object. My COM component is automatically registered when
[quoted text clipped - 10 lines]
>
> Mervin Williams