>I have created a COM object that will be used from within an application and outside the application. (It's a middle-tier data warehousing object.) It was originally written for a specific client to be used outside the application, but now mangement wants to include it with the application. So, what's the problem? Most of the clients already have the application installed, and to use it as a com object, they would have to install it and register it on each client machine. The other option is to install and register it on the server once and use createobjectex(). The problem is the name of the remote server (machine name) will be different for each installation. Is there a way to get the machine name of a remote server programmatically? Does anyone have any suggestions?
Require it to be installed in MTS if installed remotely. Then export a client setup from MTS and install that on each workstation. All you'll have to do in that case is CREATEOBJECT(). For local installs, you can bracket the MTS code in the component and test to see if it is running in MTS.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer