Deployment COM Interop question

Hello All,

I have a .NET component which needs to be deployed on the target machine so
that It can be exposed to the COM world. On the development machine, the
'register for com interop' setting when set to true, does the trick. When I
deploy it on a target machine (I am using Installshield Professional 6.3)
how do I register the assembly? Has anybody done it through installshield?
The other thing is when If I copy this assembly on the target machine, and
run regasm MyAssembly.dll, I can see the Object in the OLE / COM viewer but
not the interface which this object implements. Am I doing something wrong.
The tlb that is generated during the build is a separate file and its not
embedded in the dll.

Any inputs?

davguy
Thu Feb 26 14:54:54 CST 2004

Set the Register property on your Assembly/Project Output Group in the
Setup project to vsdraCOM.

---
David Guyer - VBQA Deployment Testing
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>From: "Saurabh" <saurabh@nagpurcity.net>
>Subject: Deployment COM Interop question
>Date: Wed, 25 Feb 2004 11:41:09 -0000
>Lines: 16
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
>Message-ID: <eLe3PQ5#DHA.684@tk2msftngp13.phx.gbl>
>Newsgroups: microsoft.public.dotnet.framework.windowsforms
>NNTP-Posting-Host: 193.133.133.230
>Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
>Xref: cpmsftngxa06.phx.gbl
microsoft.public.dotnet.framework.windowsforms:62572
>X-Tomcat-NG: microsoft.public.dotnet.framework.windowsforms
>
>Hello All,
>
>I have a .NET component which needs to be deployed on the target machine so
>that It can be exposed to the COM world. On the development machine, the
>'register for com interop' setting when set to true, does the trick. When I
>deploy it on a target machine (I am using Installshield Professional 6.3)
>how do I register the assembly? Has anybody done it through installshield?
>The other thing is when If I copy this assembly on the target machine, and
>run regasm MyAssembly.dll, I can see the Object in the OLE / COM viewer but
>not the interface which this object implements. Am I doing something wrong.
>The tlb that is generated during the build is a separate file and its not
>embedded in the dll.
>
>Any inputs?
>
>
>

Saurabh
Fri Feb 27 04:55:59 CST 2004

I am using Installshield Professional 6.3 and I could not find the property
to set which you have mentioned.

--Saurabh

"David Guyer [MS]" <davguy@online.microsoft.com> wrote in message
news:q1piErK$DHA.2196@cpmsftngxa06.phx.gbl...
> Set the Register property on your Assembly/Project Output Group in the
> Setup project to vsdraCOM.
>
> ---
> David Guyer - VBQA Deployment Testing
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> --------------------
> >From: "Saurabh" <saurabh@nagpurcity.net>
> >Subject: Deployment COM Interop question
> >Date: Wed, 25 Feb 2004 11:41:09 -0000
> >Lines: 16
> >X-Priority: 3
> >X-MSMail-Priority: Normal
> >X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
> >Message-ID: <eLe3PQ5#DHA.684@tk2msftngp13.phx.gbl>
> >Newsgroups: microsoft.public.dotnet.framework.windowsforms
> >NNTP-Posting-Host: 193.133.133.230
> >Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
> >Xref: cpmsftngxa06.phx.gbl
> microsoft.public.dotnet.framework.windowsforms:62572
> >X-Tomcat-NG: microsoft.public.dotnet.framework.windowsforms
> >
> >Hello All,
> >
> >I have a .NET component which needs to be deployed on the target machine
so
> >that It can be exposed to the COM world. On the development machine, the
> >'register for com interop' setting when set to true, does the trick. When
I
> >deploy it on a target machine (I am using Installshield Professional 6.3)
> >how do I register the assembly? Has anybody done it through
installshield?
> >The other thing is when If I copy this assembly on the target machine,
and
> >run regasm MyAssembly.dll, I can see the Object in the OLE / COM viewer
but
> >not the interface which this object implements. Am I doing something
wrong.
> >The tlb that is generated during the build is a separate file and its not
> >embedded in the dll.
> >
> >Any inputs?
> >
> >
> >
>

davguy
Thu Mar 04 14:10:08 CST 2004


I'm not very familiar with InstallShield... you should probably check with
them to see if they support registering .NET Assemblies for COM Interop.


---
David Guyer - VBQA Deployment Testing
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>From: "Saurabh" <saurabh@nagpurcity.net>
>References: <eLe3PQ5#DHA.684@tk2msftngp13.phx.gbl>
<q1piErK$DHA.2196@cpmsftngxa06.phx.gbl>
>Subject: Re: Deployment COM Interop question
>Date: Fri, 27 Feb 2004 10:55:59 -0000
>Lines: 57
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
>Message-ID: <e0AUUAS$DHA.1796@TK2MSFTNGP12.phx.gbl>
>Newsgroups: microsoft.public.dotnet.framework.windowsforms
>NNTP-Posting-Host: 193.133.133.230
>Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
>Xref: cpmsftngxa06.phx.gbl
microsoft.public.dotnet.framework.windowsforms:62746
>X-Tomcat-NG: microsoft.public.dotnet.framework.windowsforms
>
>I am using Installshield Professional 6.3 and I could not find the property
>to set which you have mentioned.
>
>--Saurabh
>
>"David Guyer [MS]" <davguy@online.microsoft.com> wrote in message
>news:q1piErK$DHA.2196@cpmsftngxa06.phx.gbl...
>> Set the Register property on your Assembly/Project Output Group in the
>> Setup project to vsdraCOM.
>>
>> ---
>> David Guyer - VBQA Deployment Testing
>> This posting is provided "AS IS" with no warranties, and confers no
>rights.
>> --------------------
>> >From: "Saurabh" <saurabh@nagpurcity.net>
>> >Subject: Deployment COM Interop question
>> >Date: Wed, 25 Feb 2004 11:41:09 -0000
>> >Lines: 16
>> >X-Priority: 3
>> >X-MSMail-Priority: Normal
>> >X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
>> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
>> >Message-ID: <eLe3PQ5#DHA.684@tk2msftngp13.phx.gbl>
>> >Newsgroups: microsoft.public.dotnet.framework.windowsforms
>> >NNTP-Posting-Host: 193.133.133.230
>> >Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
>> >Xref: cpmsftngxa06.phx.gbl
>> microsoft.public.dotnet.framework.windowsforms:62572
>> >X-Tomcat-NG: microsoft.public.dotnet.framework.windowsforms
>> >
>> >Hello All,
>> >
>> >I have a .NET component which needs to be deployed on the target machine
>so
>> >that It can be exposed to the COM world. On the development machine, the
>> >'register for com interop' setting when set to true, does the trick.
When
>I
>> >deploy it on a target machine (I am using Installshield Professional
6.3)
>> >how do I register the assembly? Has anybody done it through
>installshield?
>> >The other thing is when If I copy this assembly on the target machine,
>and
>> >run regasm MyAssembly.dll, I can see the Object in the OLE / COM viewer
>but
>> >not the interface which this object implements. Am I doing something
>wrong.
>> >The tlb that is generated during the build is a separate file and its
not
>> >embedded in the dll.
>> >
>> >Any inputs?
>> >
>> >
>> >
>>
>
>
>