In an earlier BLOG I show how extensible LINQPad is.  I encountered an odd behavior when attempting to attach to LINQPad while debugging from my Vista box.  It didn't work; at least not directly (works great from my XP box at work).

Oddly, the behavior under Vista, when the following steps are not complied with, is that the Visual Studio Debugger treats LINQPad like a Web application; a Script Documents folder appears and there will be two scripts shown.   The scripts contain the HTML contents of the top and bottom LINQPad windows and my breakpoints in code are not respected.

The work-around requires me to follow these steps - when complied with I can consistently step into my code.

1. With Visual Studio 2008 opened set my breakpoint
2. Launch LINQPad and open script (do not run)
3. In Visual Studio
   • Click on Debug
   • Attach to process
   • Select LINQPad
   • Click Attach button
   • The breakpoint in Visual Studio will complain (won't be solid circle)
4. Switch back to LINQPad and run script.  For the duration of the attached debugging session debugging will work.  Once you stop debugging you'll have to exit LINQPad and start over from step 2 above.

Note: I thought perhaps the problem was that I hadn't yet installed Visual Studio SP1 (long process) so I installed it and have the same behavior.