DCOM Server question
-
I have written an ATL COM server in a DLL with merged proxy/stub using Visual Studio 2005. It can sometimes be used locally and other times remotely. Deploying locally is straightforward and I've now got a client using it that way. However I've been wading through all sorts of internet articles, discussions etc. about how to deploy, debug, and use the component remotely, but to no avail. I need to be able to deploy and debug on a remote machine via peer-to-peer and/or ethernet switched networks, including guidance on how to configure the security correctly on Windows XP Prof. with SP 2. I've got to believe there is a 'step by step' guide on how to do this, but I haven't found one yet. Please can anyone help. Thanks.
-
I have written an ATL COM server in a DLL with merged proxy/stub using Visual Studio 2005. It can sometimes be used locally and other times remotely. Deploying locally is straightforward and I've now got a client using it that way. However I've been wading through all sorts of internet articles, discussions etc. about how to deploy, debug, and use the component remotely, but to no avail. I need to be able to deploy and debug on a remote machine via peer-to-peer and/or ethernet switched networks, including guidance on how to configure the security correctly on Windows XP Prof. with SP 2. I've got to believe there is a 'step by step' guide on how to do this, but I haven't found one yet. Please can anyone help. Thanks.
Hey, i always register my dll in com+ as application. Than you can export this application in a msi file. You can deploy for clientside and serverside. The security thing is a try and error. Good luck ;-)