Make sure your drive is defragmented, as that can slow things down. Also,
what RPM drive are you running. A 7200 RPM drive beats the snot out of a
5600 when there is disk swapping and can make a noticeable difference.

Another factor is how much of the site is in other libs, etc. and how they
are compiled (ngened, etc.). You are likely spending a lot of time JITting
the site, the libs, etc.

To speed this up, a bit, you can compile the libs and then reference the
compiled libs. You will still have JIT time, but it seems to go a bit faster
when I do thsi. It may or may not help you. Moving code from your site into
libs can also speed things up.

Another option, althought more involved, is to open the site in your browser
and then link VS debugger to that process. You will still experience some
JIT slowdown, but you will be hooked in a bit faster. Depending on the page
you are testing, this may make things MUCH faster.

Oh, and watch out for having multiple websites in a single solution. Even
though you are only debugging one, the fact you are dealing with others can
slow things down. not sure why this is, other than intial compile to MSIL,
but it seems to be that way (maybe I need to time it?).

*************************************************