visual-studio-debugging

I know I can control the way Visual Studio handles exceptions according to their type and to the fact that they're eventually caught using the "Exception" dialog. However, I've got a library that's internally throwing (and catching) an ArgumentOutOfRange exception when I'm calling a specific method. The exception is thrown (and caught by the library) maybe 1% of the time, but I'm calling this method a lot. The editor says it's by design (and indeed, the design they've chosen makes sense). The thing is that I don't want Visual Studio to break each time the exception is thrown. I don't want to

When stepping through the following sample code in Visual Studio 2012: std::vector<int> test; test.resize(1); test[0] = 4; I can set a watch on test and inspect its 0th element. However, if I set a watch on test[0], I get the error 'no operator "[]" matches these operands': How can I inspect the value of test[0] directly? I found one solution which does not depend on the internals of the class. The expanded form of the operator call seems to work for me. In this case it's the following code: v.operator[](0) I tested it in Visual C++ 2012. As @NateKohl noted, in Visual Studio 2012 (and possibly

Every time I try to debug one of my apps I get the below error message. Anyone have any ideas? I tried running Visual Studio in safe mode but I get the same thing. I also tried to repair the install and completely reinstall it with no luck :(. The full Problem Signature is this: Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: devenv.exe Problem Signature 02: 11.0.50727.1 Problem Signature 03: 5011ecaa Problem Signature 04: Microsoft.IntelliTrace.Package.11.0.0 Problem Signature 05: 11.0.50727.1 Problem Signature 06: 5011dad8 Problem Signature 07: 311 Problem Signature 08:

In my project I have a heavy part of code that should be executed on a separate thread without blocking UI. When debugger hits the breakpoint inside this code, VS2015 freezes for 5-10 seconds. After that, if I try to continue debug (by pressing Step Over, Step In or Continue), the app goes from paused state to working state, Debugging Tools are ticking, but nothing happens and there's 0% of CPU utilization. If I press Break All then, the "cursor" (don't know the correct term) is shown at Application.Run( new Form1() ); in Program.cs where Main() is. As I'm pretty new to C#, I thought that

Yes, I know there are four Memory windows, but I much prefer the display of a single value in the watch window, and I'm wondering if it's possible to specify a memory location to watch in the watch window. Putting the address by itself just evaluates to the address in hex. If you want to watch a particular memory location then you need to tell the debugger the type of the object that lives in that location. Instead of just 0x00aabbcc use (SomeType*)0x00aabbcc . Once the debugger knows the type of the memory location it will treat it just like a typed local and display values accordingly

I got a break point on the first line of Application_Start() , but Visual Studio wont break on it. Visual Studio have attached itself to the IIS working process: Auto-attach to process '[2092] w3wp.exe' on machine 'SRD00510' succeeded. My breakpoint in the home controller do work. update I've tried: iisreset restarted visual studio Rebooted. Tried to reinstall aspnet ( aspnet_regiis -i ) Reading your question, I assume you are using IIS for debugging, not Visual Studio Development Server. In this case, debugging application start is tricky, because it is only called once when the application