Todays F# debugger makes it often difficult to inspect certain symbols that are in scope from the code standpoint, but not from the debugger's.

99% of the time, when someone right clicks and selects Quickwatch, they want to know what the value of the variable is. Now, you have to scroll down the list to the Text attribute.

Place the Text attribute as well as any other attribute that most people want to see during routine debugging at the TOP of the attribute list.

The new Intellitrace for production seems like a great product but so far it doesn't seem to be enabled for Windows Services, I'm willing to have to restart the service so Intellitrace starts capturing information and to stop the service to stop the capture. When production problems occurr on services logging is the only option at times and it can be a lot of work, having the intellitrace enabled for it would be a great feature.

Make the stack trace window (that you can open when watching an object of type Exception in runtime) have links to the methods it lists, so once the programmer clicks on a link, he would easily be brought to the code file and method he needs to inspect.

Visual Studio has Edit And Continue, but I have to pause the program to change the code, which isn't very convenient. Eclipse (or the Java Virtual Machine?) has a feature that lets you change code while debugging without pausing execution. All you have to do is hit Ctrl+S to apply the code changes.
Please add something similar to what Eclipse does when debugging.

When watching a variable that is an instance of a large structured type in the watch window , it can be tedious to find the attribute of the instance you're looking for, even more when this type has a lot of nested large structured types instances as member variables. It would be nice to be able to display only the attributes whose names match a regexp or even a simple string.

When debugging a Web application, the "Run" button in VS2012 shows all installed browsers and allows the developer to select a browser to use as the debugging client container. However, when debugging a WPF/XBAP application, this option is not avaiable. This forces the developer to jump through hoops to test a WPF application for multiple browsers. Could you please add the browser selector to the "Run" button for WPF/XBAP application types?

In the exceptions window I can set the debugger to stop when exceptions are thrown, even if they're inside a try/catch block, but I only usually care about doing this for my code. Various third party libraries throw exceptions internally for whatever reason and I generally don't care about those, as those libraries will generally allow the exception to bubble up if it's something I care about.

I'd love it if there was an option to select exceptions that are "thrown in my code" or something to that effect.

For web developers, it would be of great help if the Attach to Process window showed also the associated application pools of w3wp processes - this would end a lot of PID-guessing or external scripts to be run and hence save valuable development time.

It would be really useful if there was full support for debug registers, allowing users to set data breakpoints so execution breaks not only on value changes but on value/address writes or reads.

I spend a great deal of time in VS debugger on a vary large Intel Visual Fortran project. I don't know how language dependent such a thing would be, but what I would like is the ability to setup a break "point" that is not tied to any specific line of code, but rather to a specific variable. And then the debugger would break when that variable changes value (with conditions). I often don't know where in the code anerroneous value is getting set and this would save a tremendous amount of time for me.

If I'm debugging a statement looking like this:

FunctionA( FunctionB(), FunctionC() );

and I step in to this statement, I don’t want to jump directly into FunctionB. Instead I would like the debugger to move the yellow highligt to only highlight FunctionB(), and give me the choice to step into FunctionB, or step over to move the highlight to the next sub statement FunctionC().

This would also be nice to have when tracing back in the call stack to see exactly what sub statement a call originated from, not just the entire line of code.

Web config file gets pretty big very quickly. It is very hard sometimes to figure out which part is causing the problems. Any automation will be an improvement over the curent state.

It's necessary to support "edit and continue" feature while debugging Silverlight applications.

Source files would not be locked while the debugger was attached to a running process. After the developer makes changes, they would instruct the IDE to build and update the modified assemblies in the attached debugger. This would include changes to any attached process, including w3wp.

I assume this would work best if it was done at a low-level, such that a savvy developer could modify the disassembly of source-less code if desired.

Currently (vs2012 pro) the Concurrency Visualizer displays a general category as a thread name (Main Thread, Worker Thread, ...). It would be really helpful to display the name set with SetThreadName.

Since the debugger can do it the concurrency visualizer should be able to do the same, I guess?