Re: DCOM

I have all this working now.  Thanks for all the great feedback!

For my own education,

1) I have always exported client proxies from within a COM+ package. So,
the surrogate process is always DLLHOST.EXE, correct?  And, the export 'w=
izard'
does everything for me.  Exactly what is being done with this wizard?  I
assume it is building identification info about the server hosting the CO=
M
Object, but what else is it doing?

2) What if I cannot create a COM+ package on the server, for whatever rea=
sons.
 How do I host my COM Object in 'another process' and how do I export a
client proxy?




>-- Original Message --
>Date:         Tue, 8 Oct 2002 23:28:47 +0100
>Reply-To:     Technical discussion of VBCOM <[email protected]>
>From:         Andrewg <[email protected]>
>Subject: Re: [VBCOM] DCOM
>To:           [email protected]
>
>
>You can't remote a DLL by itself - you must host it in a surrogate
>process, for example MTS, or COM+ - kind of makes sense as you can't
>execute a dll on it's own without first loading it up into a process.
>
>If you want to host your .NET component in COM+ you must derive it from
>ServicedComponent and assign the correct attributes. You'll then be able=

>to register it using regsvcs, or use dynamic assembly registration. I
>would suggest you register it and then export the client proxy and
>install that on any client machine. Access to the .NET component running=

>in COM+ will be through DCOM. You don't need to register it in the GAC
>nor do you have to give the thing a strong name. Visual Studio.NET
>support building .NET components for COM - you'll find a check box in
>the build properties that will handle registration and export of the COM=

>tlb.
>
>Hope this helps
>A
>
>
>-----Original Message-----
>From: Technical discussion of VBCOM [mailto:[email protected]]
>On Behalf Of Greg Robinson
>Sent: 08 October 2002 20:53
>To: [email protected]
>Subject: Re: [VBCOM] DCOM
>
>guess I should have said I cannot install a new component, rather I can
>install a component that is already registered into a com+ package.
>
>
>>-- Original Message --
>>Date:         Tue, 8 Oct 2002 15:20:43 -0400
>>Reply-To:     Technical discussion of VBCOM <[email protected]>=

>>From:         Greg Robinson <[email protected]>
>>Subject: Re: [VBCOM] DCOM
>>To:           [email protected]
>>
>>
>>actually, I cannot create a com+ package as the physical dll file was
>built
>>with the .net sdk regasm tool.   Unless I am wrong?
>>
>>
>>Original Message --
>>>Date:         Tue, 8 Oct 2002 14:06:17 -0500
>>>Reply-To:     Technical discussion of VBCOM
><[email protected]>
>>>From:         Donnetto De Antoni <[email protected]>
>>>Subject: Re: [VBCOM] DCOM
>>>To:           [email protected]
>>>
>>>
>>>
>>>Attachment: BDY.TXT
>>>
>>
>>
>>
>>Greg Robinson
>>Director of Training and .NET Technologies
>>Scribble Software and Training
>>www.scribblesoftware.com
>>www.scribbletraining.com
>>
>>You can read messages from the VBCOM archive, unsubscribe from VBCOM,
>or
>>subscribe to other DevelopMentor lists at http://discuss.develop.com.
>
>
>
>Greg Robinson
>Director of Training and .NET Technologies
>Scribble Software and Training
>www.scribblesoftware.com
>www.scribbletraining.com
>
>You can read messages from the VBCOM archive, unsubscribe from VBCOM, or=

>subscribe to other DevelopMentor lists at http://discuss.develop.com.
>
>You can read messages from the VBCOM archive, unsubscribe from VBCOM, or=

>subscribe to other DevelopMentor lists at http://discuss.develop.com.



Greg Robinson
Director of Training and .NET Technologies
Scribble Software and Training
www.scribblesoftware.com
www.scribbletraining.com

You can read messages from the VBCOM archive, unsubscribe from VBCOM, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.