One of the utility killers of edit and continue in web development is that when you stop debugging, it always stops the webserver. Which means you have to start debugging again just to test tiny code changes where a quicker build would suffice.
If they haven't fixed that, to me anything the do to edit and continue is fairly moot.
I'm confused, the whole point of EaC is to not have to stop the debugger? I would hazard a guess you're not debugging on iis, as detaching a debugger certainly doesn't stop the webserver.
There's a whole list of things you still can't do while EaC is running. So you're going to have to stop it a lot, EaC might help when debugging or tweaking, but for new code you're going to have it off.
They even confirm this stupid behaviour in this blog post:
That does sound annoying, IIS (non-express) seems to not have this issue though. Agree with debugging and tweaking though, my largest complaint is that you can't edit methods that contain lambda expressions.
Your other option is to detach the debugger (Debug->Detach All): stops the debugging experience in VS, while keeping the webserver process alive. Little more clumsy than clicking the stop debug button, but gives you what you want
If they haven't fixed that, to me anything the do to edit and continue is fairly moot.