IIS Express for Asp.Net kernel does not work in debug mode in Chrome

I am learning ASP.NET Core using Visual Studio 2017 Community Edition. When I start a project, I usually click on the IIS Express button at the top of the IDE. This action launches a new window in Chrome (my default browser), which until now has worked perfectly.

Today, however, it does not download the application. The browser says: "Your application is starting ..." and remains in this state. In the end, I close the window and find that the application is still running in VS. I press the Stop Debugging button, which in a minute gives me the following message:

Debugging is being stopped but is not yet complete. You can force debugging to stop immediately, but any process being detached may be terminated instead. 

This window will automatically close when the debugging has completely stopped. 

And there is a Stop Now button that I click. When I do this, exit the diagnostic hub:

Cannot access a disposed object.
Object name: 'StandardClientTransportConnection'.

I have various workarounds. I can run the project:

  • No debugging in any browser.
  • With debugging in IE or Edge.
  • By clicking on the name of the project instead of IIS Express, which I believe runs the application in regular IIS.

But I would like to understand the question that I have. I tried the following:

  • Delete the .nuget folder in my profile.
  • Delete the IIS Express folder in the My Documents folder.
  • Delete browser data from Chrome.

All without effect.

+4
source share
1 answer

It looks like the Chrome update has debugged from Visual Studio. This answer works:

Visual Studio 2017, cannot debug or launch an application

+2
source

Source: https://habr.com/ru/post/1683712/


All Articles