Previously in 2012, if I debugged in Chrome (for example), and then stopped the debugger, the website would remain running in IIS Express. This no longer seems to be the case in 2013.
Is this a new change that I need to make? How can I keep the website instance running even after I stop the debugger? Thanks.
Turning off the new "Enable Edit and Continue" feature fixed it for me.
Update 1 :
You can also turn it off on a per project basis.
Update 2 : Blog article that discusses this feature.
Easier solution:
From Debug
menu select Start Without Debugging
or Ctrl+F5
to run the project, it will keep running your project unless you quit IIS .
I didn't have "Enable Edit and Continue" in my web project's properties (VS2015 Community Update 2), but finally I found a useful comment in this link which mentioned in Rick's answer :
Christian: You don't need to turn the option off for IIS express to keep running. All you need to do is instead of stopping your application, detach all processes. If you go: Tools > Customize > click the commands tab. Then select toolbar radio button and on the drop down next to this select debug. You then want to "Add Command…". On Add Command window select debug and scroll down to and click on "Detach All". Click OK and then just close. You will see a red cross next to your debug menu. When you click this after debugging your application IIS Express will continue to run.
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.