+1 for edit and continue not working. It rarely does what it says on the tin. Usually in our case as we have 64-bit COM binary dependencies, we can't use it anyway as it doesn't work in 64-bit CLR processes. In 32-bit processes it throws the HRESULT of death MsgBox and dies.
Regarding ASP.Net debugging, I have to resort to the same thing. We actually have a set of custom framework assemblies as a last resort debugging tool that we load into the GAC in a VMware instance which have gone through a tool I wrote using Mono.Cecil that makes all members and classes public and not sealed. They all have exported PDBs as well from MS symbol server so we can step through :)
However, Visual Studio would get a fuck ton more love from me if it didn't crash 8 times a day as well. It's so damn unreliable.
My "other world" of gcc + C + vim + Linux is far more pleasant.
Regarding ASP.Net debugging, I have to resort to the same thing. We actually have a set of custom framework assemblies as a last resort debugging tool that we load into the GAC in a VMware instance which have gone through a tool I wrote using Mono.Cecil that makes all members and classes public and not sealed. They all have exported PDBs as well from MS symbol server so we can step through :)
However, Visual Studio would get a fuck ton more love from me if it didn't crash 8 times a day as well. It's so damn unreliable.
My "other world" of gcc + C + vim + Linux is far more pleasant.