title: .net debugging on production server
body: <p>My team and I are working on a .net web app project for the first time.  We want to know the most effective way to debug issues on a production server.  Currently, we ftp upload our work to a client's production server.  </p>
  
  <p>Since our background is in LAMP, we're using to SSHing into the production server, and using a combination of die(), print_r() and comment out techniques to troubleshoot the problem.</p>
  
  <p>Unless I misunderstand the way .net work, I don't think i can use the same approach because changes to .net code behind requires a complete re-build of the project (on localhost), then an upload.  This is too time consuming....</p>
  
  <p>Is there a better way to troubleshoot issues on a production server?</p>