#Visual studio remote debugging windows 10 install#
Using some of the modern support technologies such as NTRsupport, this is fairly easy to do, and by using WinDbg and the SOS Debugging Extension it is possible to install very little on the target machine while still being able to get enough data to diagnose the problem. In those scenarios, it would be nice get access to the customer’s machine. Still, it’s impossible to test all possible configurations, and so all too often bugs turn up. Build systems try to ensure that the hidden dependencies are brought to the surface, and large collections of untainted virtual machines allow you to quickly test an application in a clean room environment. Of course, it’s not really quite like that. Then, you’re totally disappointed when you copy the executable to another machine and it crashes.
You’ve configured your machine the way you like it, you’ve installed all manner of add-ins into Visual Studio, you’ve added a number of seemingly random assemblies to your global assembly cache. Remote Debugging in Visual Studio: Squashing Bugs in their Native Environment - Simple TalkĪs a developer, you get to write your application in a little sandbox that’s isolated from the real world.
0 kommentar(er)
