Greg Robinson
2002-10-16 13:06:44 UTC
I have always had control over my clients (usually just another server)
when using DCOM. On my current project, I do not. We developed a DCOM
Object that will run on a server that hundreds of clients will remote to.
I exported a client side proxy that we run locally for testing. I would
rather not have to ask hundreds of clients to run the setup file on their
workstations. I would like this to be invisible to them.
Is there a way I can 'hide' this or 'install this for them' without their
knowledge? Our exe also runs on their workstations and we do monthly updates.
I was thinking of adding some script that shells out to the set up program
and runs it for them.
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.
when using DCOM. On my current project, I do not. We developed a DCOM
Object that will run on a server that hundreds of clients will remote to.
I exported a client side proxy that we run locally for testing. I would
rather not have to ask hundreds of clients to run the setup file on their
workstations. I would like this to be invisible to them.
Is there a way I can 'hide' this or 'install this for them' without their
knowledge? Our exe also runs on their workstations and we do monthly updates.
I was thinking of adding some script that shells out to the set up program
and runs it for them.
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.