Ending the debug session in Visual Studio 2013 Preview kills IISExpress, and how to fix it

It seems that by default when you end the debugging session of an ASP.Net app in Visual Studio 2013 Preview, it will kill the IISExpress instance as well. This is fairly annoying as my workflow usually involves leaving the browser window open and just doing a new build, and then refreshing the browser. Fortunately it was an easy fix, all you need to do is go the the project properties for the web application, go to the web tab, and uncheck “Enable Edit and Continue”.

I hope that this is just a bug and will be fixed in the final release of VS2013, as the idea of finally getting edit and continue back is cool, but not at the expense of killing IISExpress.

  • Andrew Hall (MSFT)

    At this point in time the .NET runtime does not support Edit and Continue on attach, so unfortunately you will need to choose Edit and Continue or keeping IIS Express running. This behavior will not change in the RTM version of 2013.

  • Matthew Nichols

    I have the same workflow and have been mildly annoyed at this. I was assuming that I would just have to start setting up IIS for all of my projects since that is not effected. Not really worried about Edit-and-Continue myself. Thanks for the tip.

    Matthew