How do I remote debug an ATL server dll using VS .NET 2003?

Remote debugging is working fine for the client application, and I have no
problem debugging the dll locally (by pointing to the local client app).

If I specify the remote client app in the "Debugging->Remote Command"
setting (in the dll project), the breakpoints in the dll code are not "hit".

Any suggestions are much appreciated.

Henrik

--------------------
[quoted text, click to view]

Henrik:
A couple questions:
1. Does remote debugging to the machine in question work in general (i.e.
can you remotely debug a non-ATLS dll?)
2. Does the debugger auto-attach to Inetinfo on the remote machine? (Should
say so in one of the first lines of text in the Debug pane of the Output
window when you start debugging.)

I had not done this before but was able to get it to work by following the
help topics on it.

You may want to try reseting IIS ("iisreset" in a command prompt.)
Sometimes this is necessary if the debugger hasn't been able to clean up
after itself properly (which is always a possibility with most any
debugger.)

One other thing you might try is to manually attach the debugger to
inetinfo.exe on the remote machine rather than relying on auto-attach.

--
Mike Forkey
Visual C++ Team
This posting is provided AS IS with no warranties, and confers no rights.