Re: DCOM Server configuration question

From:

"Igor Tandetnik" <itandetnik@mvps.org>

Newsgroups:

microsoft.public.vc.atl

Date:

Mon, 18 Feb 2008 16:37:40 -0500

Message-ID:

<uku39ZncIHA.2268@TK2MSFTNGP02.phx.gbl>

"Peter" <peteATkapiti.co.nz> wrote in message
news:ONDObUncIHA.1184@TK2MSFTNGP04.phx.gbl

"Igor Tandetnik" <itandetnik@mvps.org> wrote in message
news:uKsll5mcIHA.3932@TK2MSFTNGP05.phx.gbl...

"Peter" <peteATkapiti.co.nz> wrote in message
news:OSI3vhmcIHA.1208@TK2MSFTNGP03.phx.gbl

Thanks Igor, but what I'm after is the exact opposite: a single
IIS/ASP web application running on machine A which talks to two
instances of my DCOM component, one running on machine B and the
other on machine C.

The last parameter of CreateObject lets you specify which server to
create the COM object on. Call it twice, to create two instances on
two different machines.

But this will have to be accomplished in ASP/VBScript and I can't see
that "last parameter" when using the ASP Server object's CreateObject
method:
Server.CreateObject("MyComponent.MyInterface")

I must admit I know little about ASP. Can't you use the function built
into VBScript?

http://msdn2.microsoft.com/en-us/library/dcw63t7z.aspx

If push comes to shove, write a tiny in-proc (DLL) server whose only job
would be to create and return the real COM object on an appropriate
machine. See CoCreateInstanceEx.
--
With best wishes,
Igor Tandetnik

With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925