Re: DCOM Server configuration question

From:

"Willy Denoyette [MVP]" <willy.denoyette@telenet.be>

Newsgroups:

microsoft.public.vc.atl

Date:

Mon, 18 Feb 2008 22:46:17 +0100

Message-ID:

<OVY7xencIHA.5164@TK2MSFTNGP03.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")

Pete

The last parameter is optional, when specified it indicates the server name
where you want the object to be instantiated..

CreateObject("someObject", "someServerName")

Willy.