Debugging TIP of the Day
If you are like me, you probably have a overall project that consists of many solutions. For whatever reasons it doesn't make sense to have the various solutions and projects all included into a single solution. That makes debugging rather difficult - especially difficult when say solution #2 only gets invoked when a web project, console application, or other is 'live'.
With VS2005 and above you can actually multi-select the wp3svc, service hosts etc and the debugger of whatever solution will go into a pull down mode where it will allow you to step through the other projects in the other solutions via the particular solution you are working with. Naturally, all of the other solutions should already be compiled in debug mode and the corresponding meta data from the debug symbols can be stepped through.
If using VS on a 64 bit system, the only way to actually change code on the fly during debugging is if the code being changed is referenced from an outside solution. However, please not that any code changes you make will still have to be made to solution being pulled down. For whatever reasons if the solution you open on a 64 bit system, can not be directly modified if the debug attach process is within that solution. Confusing - you'll get it if you try it.
The multi-select is a great way to debug as it it means no fancy footwork has to be done to step through the various application that requires multiple solutions.
Simply Select "Debug" - "Attach To Process" and multi-select whatever the various solutions use.