IIS Express Immediately shutting-down running site after stopping web application
I recently faced a similar situation when suddenly my IIS Express stopped right after I stopped debugging. This happened after I turned on "Enable Edit and Continue". So if you disable this you will see that IIS Express stays running even after debugging is stopped.
Right click your project > click Properties > select the 'Web' tab on the left > uncheck the Enable Edit and Continue
checkbox.
IIS Express stops suddenly when I click on a text box in my web app
I was having same Problem with Visual Studio (15.7.5)
& Firefox Developer Edition (62.0b12)
. Every time i click any input or text field it just closes both Firefox and IIS without any error or exception.
What i've done to fix this issue is i Simply Uncheck the option:
Stop Debugger when browser window is closed
found under Tools > Options > Projects and Solutions > Web Projects
save
, clean
, Build
& Start
.
This one Fix my Problem!
Stop IIS Express exiting automatically
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.
After installing VS 2015 Update 2, IIS Express closes when I stop debugging
This issue has been resolved in Visual Studio 2015 Update 3. Read the release notes here.
Web Developer Tools
For ASP.NET Web Application projects, when "Enable Edit and Continue" checkbox is unchecked, the IIS Express process will no longer stop
every time you stop debugging.
Why does IIS Express shut down the Application and restart it all the time?
Found it. My code lives in the Dropbox folder, and apparently Dropbox changes something inside the web project's bin folder.
When I deactivate Dropbox, the problem goes away.
IIS Express crashes when starting a site from visual studio
In your project folder find the hidden .vs folder and delete it. This solved the problem for me.
My web application continues to run after stopping the debugger.
As far as I know, Visual Studio just does this sometimes and there's not anything you can do about it. If it's happening consistently I would try reinstalling and/or reverting to older versions to see if the issue persists.
Related Topics
How to Validate Signature of Jwt from Jwks Without X5C
Multiple Where Clauses with Linq Extension Methods
Custom Xmlwriter to Skip a Certain Element
Why Are There System.*.* Dlls in My Bin Release Directory
Overriding Fields or Properties in Subclasses
Auto-Resize Multiple Forms Rendered on Panel
Comboboxes Are Linked for Some Reason
Can a Tcp C# Client Receive and Send Continuously/Consecutively Without Sleep
How to Copy File - Access to the Path Is Denied
Proper Datagrid Search from Textbox in Wpf Using Mvvm
How to Merge Two Lists Using Linq
Wcf - Design Parameter Decision
How to Generate Random Color Names in C#
Center Messagebox in Parent Form
Dynamically Switch Wcf Web Service Reference Url Path Through Config File
How to Reuse Code for Selecting a Custom Dto Object for a Child Property with Ef Core