DCOM

I am using a 3rd party DLL on a web server.  This DLL is instantiated wit=
h
late binding via Server.CreateObject.

I also want to use this 3rd party DLL from client workstations using DCOM=
.
 On the web server, the IIS site is set to medium pooling, so, it is my
understanding the 3rd party DLL runs under DLLHOST.EXE.

If I want to now remote to this DLL, I will need to export a client proxy=
.
 I can do this easily by placing the DLL in a COM+ package.  However, wha=
t
if i cannot, for whatever reason, place the DLL in a COM+ package?  How
do I remote to this  DLL without COM+?  Or, how do I create the surrogate=

process for that DLL to run in and how do I create a client proxy I can
install on my client workstations?

And finally, if I do create a COM+ application and add the 3rd party DLL
to and Export a proxy from with the wizard, will this effect how my ASP
client uses the DLL?




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.