Visual Studio debugging lingers on "Connecting to the web server"

When I launch the web API application, I get the following window:

Joining the web server

It just stays that way until I canceled the cancellation.

When I click the Cancel button, this error message is displayed:

Catastrophic failure

I tried rebooting and running iisreset /restart , but it did not fix it.

Any ideas what I can do to start my debugger again?

NOTE. Web API 2 Project Server Setup is installed on Local IIS . My service is hosted by IIS, and when I am not debugging, it works great.

+6
source share
6 answers

Since I commented before I had the same problem, but now I understood the reason and found a solution.

I just got a new car last week (this problem was actually one of the reasons), and after a while I had the same problems that I could not debug my projects. Fortunately, because I installed all the updates one by one, I was able to pinpoint when it happened.

The latest update for " Microsoft ASP.NET and Web Tools " seems to be expanding something.

Unfortunately, uninstalling or repairing the web tool extension is not easy: Uninstall this extension by going to the Windows control panel and changing the installation of Visual Studio . I had to completely remove Visual Studio and reinstall it (the repair did not do the trick). You can update and install all your extensions as you wish, just make sure that you do not update the extension of web tools

I tested this on my old car, and he did the trick too.

I also created a problem on GitHub , since I will not update the extension until it is fixed, if anyone has additional information, please add it to the problem.

+3
source

I had this problem for Visual Studio 2017, and, as in the previous post, I had the Debug option "Enable the .NET Framework Basic Step". Troubleshooting fixes the problem.

+3
source

I just reset all settings for VS and it worked again.

Tools => Import and Export Settings => reset All Settings

Good luck

+2
source

In Visual Studio 2015, go to Tools β†’ Options β†’ Debugging and uncheck the β€œEnable .NET Framework Original Step” checkbox. This may be related to the problem with loading characters, so if you want to keep debugging the source of the .NET Framework, it can help find on the Internet how to clear the character cache or preload it, or install your character server, etc.

Enable .NET Framework Source Stepping

+1
source

Possible fix:

Check "Include only my code" in "Tools-> Options-> Debugging

+1
source

In Visual Studio 2017, I just restarted my machine and launched the solution, other windows did not open even in the browser, although the visual studio took a long time to open (30+ projects in the solution), the problem did not recur.

0
source

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


All Articles