"Mokles" wrote:

> Thanks Charles. It seems to be the answer I was looking for. I will try it out.
>
> The COM object is from a License protection component. They have done
> Interop thing. so I do not need to worry about it.
>
> Mokles
>
> "Charles Waudby" wrote:
>
> > If you add the COM object to the setup project one of the file properties is
> > Register and one option allows for self registration.
> >
> > That said, if the COM object is being called from .Net then you should look
> > at creating a Primary Interop Assembly and creating a merge module for it. As
> > long as you sign it, it can be installed in the GAC and you will avoid
> > version conflicts.
> >
> > Search MSDN for primary interop assemblies and COM, eg:
> >
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpcongeneratingprimaryinteropassemblies.asp
> >
> > "Mokles" wrote:
> >
> > > I would like to register a COM component on the client machine during the
> > > installation of a .Net program. Can I do it through the .Net setup project?
> > > Can someone lead to the right direction?
> > >
> > > Thanks,
> > > Chanchal