10

I am running Visual Studio 2013.

When I stop debugging my MVC application, IIS Express stops automatically. How can I stop this happening?

rhughes
  • 9,257
  • 11
  • 59
  • 87
  • 1
    I think this is was answered better here: http://stackoverflow.com/questions/19568762/how-can-i-prevent-visual-studio-2013-from-closing-my-iis-express-app-when-i-end – Spike2000 Mar 12 '14 at 22:23
  • @ChristopherLehnert That answer is good, but it requires changing project settings. The answer here doesn't. – rhughes Mar 13 '14 at 03:59

3 Answers3

9

The trick is to right click on your website and View -> View in Browser (or just View in Browser for Visual Studio 2012).

This will start the website in IIS Express and keep it running, not dependent on a debugging session being run.

rhughes
  • 9,257
  • 11
  • 59
  • 87
  • 3
    The problem is that this is new behavior. You used to be able to *View in Browser* and then launch the debugger afterwards. Upon stopping the debugger the IIS Express would continue to run. In VS 2013 it instead kills IIS Express. Huge step backward. – Yuck Mar 12 '14 at 19:17
2

One option would be to launch IIS Express manually. I believe you can also just detach from process in visual studio instead of stopping the debug session.

Community
  • 1
  • 1
beavel
  • 1,077
  • 1
  • 8
  • 16
  • But I find that VS kills manually-launched IIS Express sessions arbitrarily (especially if my webapp is inside the same solution as another desktop application when I stop debugging the desktop application). – binki Sep 05 '14 at 18:09
2

In Visual Studio 2013, Go to Tools > Options

In Debugging menu in side list find Edit and Continue

Uncheck the Enable Edit and Continue check box

This will solve your problem

Farshid
  • 5,134
  • 9
  • 59
  • 87