Visual Studio ending Debug unexpectedly (IIS error)

Question

Visual Studio ending Debug unexpectedly (IIS error)

Asked 5 years, 11 months ago

Viewed 202 times

0

I come to share a solution that for me at least worked after several attempts. But first I will explain the problem occurred:

Once using windows 7 I had a problem starting the debug of a Webapp by clicking on the url input of the browser, starting a new tab or what input my view had automatically debug and the browser was closed(The same procedures were performed in the browsers: IE, Edge, Mozilla, Chrome and Opera)

Output window always showed me IIS errors such as [12712], [6392] among others, always alternating the error but without description.

Eventviewer showed me an IIS warning:

The directory specified for caching Compressed content C: Inetpub temp IIS Temporary Compressed Files Clr4integratedapppool is invalid. Static Compression is being disabled.

I changed directory permission among other things in IIS but without success and without finding answers in forums of several countries(Maybe by search terms and error codes).

Although this information is useful, you simply posted it as an answer. Ideally you would create a question with the problem and then publish your solution as the answer.

– Leandro Angelo

2018/07/30 at 18:03
I just divided the texts...but ok done

– user24203

2018/07/31 at 17:51

1 answer

Browser other questions tagged .net visual-studio iis debug iis-express

You are not signed in. Login or sign up in order to post.

by user24203 • **117** points · Answer 1 · 2018-07-31T17:49:43+00:00

Finally I arrived at the following amendment that solved the problem inexplicably for me that was the following:

In VS go in Tools -> Options -> Projects and Solutions -> Web Projects

Disable option that says to quit Debug when browser window closes.

Really inexplicable since I didn’t close the window, the iis warning log stopped appearing, and there was no interaction before open tabs and click inputs.

However if you are someone like me who is suffering formatting Windows reinstalling their 30Gb of visual studio changing version and seeking solution without finding. It worked perfectly for me, no error presented anymore, the performance of the applications is perfect(Debug and Release).