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 that somewhere 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.

Thanks again. Not a lot of help there about this particular situation, but some useful info. none the less. Cheers.

Thanks for that. It's a pity that the DLL Wizard created a CWinApp derived class that includes Message Map macro declarations. There is a possiblity that the main applications using my DLL will not have a main frame window - they may also be ATL applications. Please could you advise what I could do in these cases? Thanks

I have a DLL that has a class derived from CWinApp. I have another class in the DLL that needs to trigger an asynchronous process within that same DLL. Since the DLL has no window I use PostThreadMessage to trigger the process as follows: void CMyClass::TriggerAsyncProc() const { AfxGetApp()->PostThreadMessage(WMU_MYMSG, 0, 0L) ; } In my class derived from CWinApp, I have tried two different methods to trap WMU_MYMSG. The first was to override PreTranslateMessage, and the second was to try to use the CWinApp message map (via ON_THREAD_MESSAGE). The DLL is being used by a dialog application, and the TriggerAsyncProc is definately sending the message because PostThreadMessage(WMU_MYMSG, 0, 0L) returns non-zero. The only thing I can think of is that my message is going through the message map of the dialog application instead of my class derived from CWinApp in the DLL. Please can someone tell me why I'm losing the message, and suggest either how I correct this or an alternative method? Thanks. :confused: