visual-studio-debugging

I regularly find it very useful when debugging to switch on the Common Language Runtime Exceptions: Thrown option in Visual Studio's Debug > Exceptions screen. I'd like a quick way of doing this, since it's always the same checkbox I'm toggling and that screen is very slow to load. In previous versions, it was possible to do this with a macro , but macros have sadly been removed from VS2012 . Does anyone know of a quick/easy way to do this with a plugin/extension/keyboard shortcut? Simon Opelt Exception Breaker is a Visual Studio (2010, 2012, 2013) plugin created by a fellow SO user for that

In the Visual Studio 2010 watch window, I found the value of a variable became -1.#IND000. What does this mean? Chun-Fu Chao IND is the representation of NaN (Not a Number) in Windows system. IND = "indeterminate form", mostly a result from an illegal operation like dividing by zero or arithmetic operation with infinity. It means the content is undefined, can result from a division by 0. 来源： https://stackoverflow.com/questions/9883128/what-does-1-ind000-mean-in-the-visual-studio-debug-window

I have an application in C++ developed in VS2010. This application has an ability to restart itself when needed (some changes that requires it to reboot). Now there's some bug that occurs only under certain circumstances on the beginning of the new instance after the restart. The problem is that I can't find out what it is, because the new instance does not have the debugger attached (VS debug mode ends with the initial instance closing). Any idea how to automatically attach a debugger to the new instance? Thank you I "discovered" how this is done after getting infected with some malware that

Some legacy code I'm stuck maintaining is stuck in an infinite loop (and thus I myself seem to be in one); I can't figure out why/how, though. Here's the app's entry point, where it instantiates the main form (frmCentral): CODE EXHIBIT A public static int Main(string [] args) { try { AppDomain currentDomain = AppDomain.CurrentDomain; currentDomain.UnhandledException += new UnhandledExceptionEventHandler(GlobalExceptionHandler); string name = Assembly.GetExecutingAssembly().GetName().Name; MessageBox.Show(string.Format("Executing assembly is {0}", name)); // TODO: Remove after testing <= this

I'm debugging a windows service which has two running instances, by attaching to both instances. I am doing this because I know only one instance will hit my breakpoint, but I'd like to know which instance that is, so that I don't have to attach to both in future. Is there a way, when attached to multiple processes, that you can tell which one has hit a breakpoint? A trial-and-error solution would be to attach one at a time and see if the breakpoint is hit, or, stop one of the services (through services.msc) and see which process ID disappears - but neither solution seems scale-able to me. Is