I previously had it working once before on another project, but that was before we put our workstations into a domain and it was a slight challenge for 30 minutes, but then all ran smoothly.
The notebook idea isn't a bad idea, but it's not really an ideal long term solution. Would be nice if there was a way to just tell Windows to dump all method calls with arguments and exceptions to the hard disk without having to do too much overhead such as tracing. I'm sure it could be done as it's similar to what most profilers do. Maybe I could possibly run a profiler thought it and find the answer with some guess work. ------------- Michael Lyons -----Original Message----- From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Maddin, Peter Sent: Monday, 9 August 2010 11:25 AM To: ozDotNet Subject: RE: Remote debugging outside of domain If I was in this position, I would install VS on a notebook (if you don't have one spare, they are pretty cheap these days) and place it in the same network environment as your server. I would then use remote debugging to discover the issue and if necessary nuke the notebook afterwards. >From all the pain you are going through, maybe a simple approach would be quicker. That being said I have only debugged services remotely within a domain (and I found that challenging enough). Regards Peter Maddin Applications Development Officer PathWest Laboratory Medicine WA Phone : +618 9473 3944 Fax : +618 9473 3982 E-Mail : peter.mad...@pathwest.wa.gov.au The contents of this e-mail transmission outside of the WAGHS network are intended solely for the named recipient's), may be confidential, and may be privileged or otherwise protected from disclosure in the public interest. The use, reproduction, disclosure or distribution of the contents of this e-mail transmission by any person other than the named recipient(s) is prohibited. If you are not a named recipient please notify the sender immediately.
