You have to install the remote debug manager first, which is not a good idea
on a server. I am not sure if there are other steps to debug a windows
service.
A better option would be a VPC with Windows 2003, but only if it works on
XP, but not on Windows 2003. Instrumenting the code to find out what is
going wrong might also be a great option, as you may just have a
configuration issue.
I would only opt for Remote Debug, if possible, as a LAST resort, esp. if
the windows service reacts to external events. Why? Every person hitting the
service (or dropping files, etc.) will fire off the debugger, which will
show up on your radar. Unless you can sort out where the bits are being
fired from in debug, you may make wrong assumptions and further muck up the
entire process.
I hope I have discouraged you against remote debugging. :-)
--
Gregory A. Beamer
*************************************************
Think Outside the Box!
*************************************************
"JLuis Estrada" <fr********@hotmail.com> wrote in message
news:%2******************@TK2MSFTNGP03.phx.gbl...
Hi there.
Id tried to find information about how to set up the remote debugging on
win2003.
I have a PC with winxpsp2 with VS2003 installed. And I developed an
winservice app that runs on the server.
This servers is fara way from here. Buts its visible over internet.
How can I debug the winservice installed on the server????
hope somebody could help me
