On Wed, Sep 2, 2009 at 3:32 PM, r...@ny<[email protected]> wrote: > > I have an old asp.net web application based on .net framework 1.1, it > has been deployed to live server for many years, right now I am having > some issues with the live site only, the development version on my > desktop works fine. So I am thinking about attach a remote debugger to > the live site and monitor what happened exactly on live server, but I > don't know how to do that. > > I used remote debugger before, but that was used when I created new > project on some development server in local LAN, and the source and > project is actually on the remote server, I just attached remote > debugger from my desktop to that server, it works fine. But I am not > sure how to debug a application on live server. > > Many thanks for your help! >
Short answer: you don't. Most people in their right minds wouldn't attach to a live process for debug. Long answer: you should be building flexible logging and tracing into your code for these scenarios. log4net and the Enterprise Library Exception Handling Application Block (EHAB) and Logging Application Block (LAB) work well for this. You can turn tracing off or on from the config file, so you wrap all operations in a trace. When you turn it on, you get a trace log of all activities, so you know where processing was at when an error occurred. Use exception handling and tunable-logging to send more or less, richer or poor, details to the log. Again, this stuff is set in the config file. You see problems, you turn it on. Problems solved? Turn it off. ∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=(andrew+badera)+OR+(andy+badera)
