I want to able to see function return value in managed debugger just like unmanaged debuger (it has this feature from Visual Studio 6.0!).

Imporve x64 debugger so Edit and Contunue works when running on Windows x64 o/s

I would really like xaml debugger! I think that this caution is necessary! very difficult to find errors in the xaml.

When I'm debugging I look with different eyes at my code. It makes me wonder what things do and it would be a great time to add some comments to the code. Unluckily (while the executing code is not changed) I can not add comments and always have to remember where I wanted to add some extra comments,

If a exception fired I would happy with a Button inside the exception dialog to disable this type of exception message. Because I am not interest on this type. Today I must go to the Debug context menu --> Exceptions --> Find --> then typing the exception type (oh how was it?) and unchecked the exception. For me to much steps. A little feature and I will be happy :-)

The "exceptions" Dialog isn't very usefull.
Somtimes i want to break on IOException somtimes on ArgumentException or a set of n other Exceptions. Everytime I have to open the Dialog serch for the Exceptions check them and close the dialog. Everytiem the same work.

It would be nice to have a "Save configuration as" Button in the Dialog to save the curretn configuration under a specific name. Later you can select a configuration via a submenu entry in the Debug-->Exceptions menu.

Improve debugging support for Ix and Rx queries in the IDE. Specifically, a condensed call stack view that was more of a "query stack" would be great. It would also be great if we could hook into the "query stack" features from our own LINQ-based APIs.

Enable "Edit and Continue" when debugging silverlight projects.

It is very annoying and fells like the 20th century that you first have to stop debugging before you make any change to the code (or comments) and then have to restart the whole application.

Add IntelliSence support or at least condition history picker

Add a Start Without Debugging option for individual projects within a solution. This should be located under the Debug context menu item under the project node within Solution Explorer and optionally all debug/run functionality should also be included under the main application's Project menu for easier keyboard access and for consistency.

If no sources are available, instead of showing x86 assembly, show .NET IL and allow to step through the IL instructions.

Under Linux reverse debugging of C++ code is possible for a while. Both by a commercial solution (UndoDB (http://undo-software.com/)) and meanwhile by GDB, too (http://www.gnu.org/s/gdb/news/reversible.html).

It's time to add this capability to the Visual Studio debugger, too.

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.

Add support to watch expressions with getters (const functions) in C++

Examples:
1.
float GetWidth() const;
float GetHeight() const;

area = obj.GetWidth() * obj.GetHeight();

2.
const float operator[](unsigned int index) const;

val = obj1[i] + obj2[i+1];

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.

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.

Config transforms change behavior that should be easily testable.
Without this option either the web.config must be edited or the app must be published.
Please add an easy way to use a config transform during debug and test without changing the web.config itself. If the config file is changed, then it would be easy to accidentally commit those changes to source control.

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.