Visual studio 2015 is waiting for the local host after the first boot for debugging

Question

I struggled with debugging on Visual Studio 2015 Community Update 1 and 2. After the first debugging session, everything worked correctly. But when I make changes during debugging and update the website, it will forever wait on the local host. This also happens if I stop debugging, make changes, and start a debugging session again. This occurs in 95% of cases. I was looking for stackoverflow and googled for similar problems, and none of the answers suggested by others fixed this problem. Only what works is to restart VS after the first debugging.

What I have tried so far:

• Removed Visual Studio 2015 and installed back.
• Purified Temp folder (which is used with IIS Express)
• Reinstall IIS 10
• VS started as administrator -
• ...... Created a completely new solution with 3 projects and copied all the code into a new solution - hoping this could fix any content problems.
• Created a new TFS project and contacted there
• Firewall temporarily disabled
• The just released Update 2 for the VS 2015 community also did not fix.
• Cleared characters also download characters from Microsoft servers.
• Disabled link to browser.

I'm running out of patience and ideas on how to fix this unpleasant problem. My guess is that something does not work after the first file upload, and then when VS tries to copy the files back to the temporary folder, it cannot or something stops working. Has anyone got any ideas?

Answer 1

Here are new things for you, I believe that one of them will solve the problem of cheers. I list from the majority that I considered the least:

• Try creating a new application pool and assign it your website. Verify user authentication for the new application pool is provided correctly.

• Set the connection timeout to something reasonable, such as 15 seconds web.config.

• Try using a local IP address instead of localhost Disable for all antivirus programs in addition to firewalls if you are using. Check the blocked ports on the firewall and change the dynamic ports of the application, if any, for fixed trusted ports.

• Someone says on the Internet: “The problem may be that the files are downloaded from the torrent and your database on another server”

• Someone on the Internet also says: "I deleted the .suo file and this fixed the problem."

This site may also help: http://dustyreagan.com/localhost-doesnt-work-cant-debug-your/

EDIT: Please check the solutions on these sites: https://marcclifton.wordpress.com/2014/05/18/page-not-rendering-with-iis-express-in-firefox-or-chrome-waiting-for- localhost /

http://codetunnel.io/how-to-debug-your-aspnet-projects-running-under-iis/

Answer 2

Sometimes it helps:

taskkill /f /im:iisexpress.exe rmdir /s /q [path to your solution]\bin rmdir /s /q [path to your solution]\obj taskkill /f /im:conhost.exe 

I have this in the wee batch file that I run before trying to deploy / debug, especially when I switch between Debug and Release modes. Basically, cleaning up objects and destroying iis express and the console host gives you a new start.

Answer 3

In my case, it was caused by SignalR performance counters (if you use SignalR). If you install them manually, waiting for the local host disappears.

A detailed description of how to set SignalR performance counters can be found on the Microsoft website: http://www.asp.net/signalr/overview/performance/signalr-performance#perfcounters

Answer 4

I solve this problem by installing vs 2017 and then vs 2015 started working