Last post Jan 18, 2019 09:25 PM by wavemaster
Jan 17, 2019 11:07 PM|wavemaster|LINK
Been actively working on a socket application using ASPNET Core and this project has become a nuisance.
Early on starting the debugger and stopping it was a matter of a few seconds.
The code is pretty much the same size as it was 30 days ago, but now starting the debugger takes upwards of 30 seconds.
Closing the debugger even longer still, enough for Windows 10 to tell me Visual Studio is not responding.
Takes too much time.
Jan 18, 2019 07:01 AM|Xing Zou|LINK
It seems to be a VS dubugger problem. For more accurate answer, you could ask on Visual Studio Forum:
Have you tested it on another machine? If other machines are good, then it may be VS settings or environmental problems,try to clean build, clean the cache, and try to create a new project to check. If you still has this problem on another machine,
roll back the code to 30 days ago to see if it solves the problem.
Jan 18, 2019 09:25 PM|wavemaster|LINK
I had to disable diagnostic tools to get it to work again.
Crazy to think that Microsoft would not fix stuff like this.