Paul posted this great NUnit tip on his blog.  Of course this also works great for ASP.NET.  Just attach to the w3wp.exe process on IIS6 or the aspnet_wp.exe process on IIS 5.X.  How do you debug something however that is part of your startup code?  This is especially tough when wanting to debug the constructor of a HREF EXE or WinForms control in the browser. Use System.Diagnostics.Debugger.Break().  This will cause a debugger prompt to pop up when the line is hit allowing you to start a new VS.NET instance or select an existing instance to debug the running application.

Thursday, March 18, 2004 9:47:16 AM (Pacific Standard Time, UTC-08:00)         Comments [0]