So, I have a question that someone here may know the answer ... I am trying to debug and track through some C # code on a remote Windows Server 2012 R2 with Visual Studio installed. I use the Debugger.Launch () call to connect to the program, and Visual Studio starts correctly and shows me the correct breakpoint.
However, as soon as I try to log in, step over or even just resume execution, the entire server will fail and reboot. Absolutely nothing is written to explain that the problem is in the event log, except for the usual message "previous reboot was unexpected." This issue occurs regardless of whether I try to debug the application as a console application or a Windows service.
Access to the server is through Remote Desktop, and the source code files are located on my local disk (for example, "\ tsclient \ X \ path \ to \ source.cs"). I’ve been trying the website for several days, trying to find something and everything that could help, but I didn’t find anything that could help. I even tried to make sure that VS was excluded from DEP, and that also did not change the end result.
This happens with Visual Studio 2012, 2013 and 2015 (all with the latest updates). In addition, all Windows updates have been applied to the server. The strangest part is that it all worked about a month or two ago, when I needed to debug another application.
So, stackoverflow guru, does anyone know a) what can cause this and b) how to fix it?
Eg
EDIT: Fixed an example of a path that angle brackets did not like. = \