# Visual Studio IDE

Welcome to the Visual Studio UserVoice site. Let us know what you would like to see in future versions of the Visual Studio suite of products. This site is for suggestions and ideas. If you need to file a bug, you can visit our Developer Community website to get started.

NOTE: The Applications Insights forum has moved to the Azure feedback site.

For suggestions for improvements to other developer products, see these sites:

To review the current UserVoice statuses and their definitions, please review our “What Does the Status of My Feedback Mean?” article.

We look forward to hearing from you!

- The Visual Studio Team

## I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

### There are two ways to get more votes:

• When an admin closes an idea you've voted on, you'll get your votes back from that idea.
• You can remove your votes from an open idea you support.
• To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

• Hot ideas
• Top ideas
• New ideas
• My feedback
1. ## Show Milliseconds for DateTime objects in the Debugger

There needs to be a way to format the way DateTime objects' value is displayed in the debugger to show the milliseconds.

Doesn't have to be a customizable format just need a format that shows milliseconds.

Vote
Check!
(thinking…)
Reset
Signed in as (Sign out)
You have left! (?) (thinking…)
• ## Make changing command line simple

Changing command line option needs me to open project properties and set command line using interaction with mouse.
I deal with app which uses command line heavily.
It would be great to have immediate/command window shortcut to change command/command line we want to use for debugging.

Vote
Check!
(thinking…)
Reset
Signed in as (Sign out)
You have left! (?) (thinking…)
• ## Save or copy Memory Usage snapshot list

I'm in a situation, in native C++, where I am replacing an algorithm by another one and I want to make sure the new algorithm does not allocate more memory than the old one. So I ran the old algorithm taking memory snapshots at relevant points. Now I have this memory snapshot list but I can't copy or save any of this information so I can reference it when I run the new algorithm. I have to eyeball and copy this information into a text file. I would be cool if I could copy the information much like we can…

Vote
Check!
(thinking…)
Reset
Signed in as (Sign out)
You have left! (?) (thinking…)
• ## add horizontal scroll bar to Locals and Watch windows

Vote
Check!
(thinking…)
Reset
Signed in as (Sign out)
You have left! (?) (thinking…)
• ## Add a "Step into outermost" to the Visual Studio debugger

While debugging, a single line of code may contain multiple function calls, but usually, when you "step into", you want to step in the outermost call. For example:

obj->getA()->getB()->Compute( x.getId(), returnStuff() );

In the code above, 9 times out of 10, you want to step into Compute(). This is what "step into outermost" would do, with a nice default shortcut like Shift-F10.

Current alternatives:
- Step into specific : going through the right-click menu is quite cumbersome, and finding the correct function is not immediate
- Alt + Shift + F11: default keyboard shortcut to "step into specific". This is…

Vote
Check!
(thinking…)
Reset
Signed in as (Sign out)
You have left! (?) (thinking…)
• ## Link Build errors to Stack Overflow solutions

When a build error occurs, it would be great if VS used deep learning to determine if that specific error has a solution on Stack Overflow. When I click on the error, it could provide the possible fix.

This would greatly improve my workflow and allow known fixes to be found easier.

Vote
Check!
(thinking…)
Reset
Signed in as (Sign out)
You have left! (?) (thinking…)
• ## Breakpoint covered the bookmark

In vs2005/2008/2010, when I set a breakpoint and a bookmark in the same line, I can see both. But in vs2012 RC, the breakpoint covered the bookmark. Maybe restore icons to vs2010 is a good idea.

Vote
Check!
(thinking…)
Reset
Signed in as (Sign out)
You have left! (?) (thinking…)
• ## Edit and continue should work for handled Exceptions too

Hi!

Visual Studio provides great debugging experience for exceptions not handled by user code. You're stopped at the call where exception occurred and can fix the code, set next statement to the fixed code and all just works (does not if you've disabled auto stack unwind but that's not our case).

However, if the exception is handled somewhere down the stack (e.g. with exception handler for logging and rethrow) the debugging becomes much more trickier. You can break on handled exception (if set in Exceptions window) but cannot unwind the stack and cannot fix the code.

My proposal is: to…

Vote
Check!
(thinking…)
Reset
Signed in as (Sign out)
You have left! (?) (thinking…)
• ## Graphics Frame Analysis : image export

It would be nice to be able to save images to a raw or png format.

Vote
Check!
(thinking…)
Reset
Signed in as (Sign out)
You have left! (?) (thinking…)
• ## Prevent editing files outside solution

Like this case here:

https://stackoverflow.com/questions/46330903/prevent-editing-files-outside-solution

Visual Studio allows developers to open an external file in order to debug it, Can we debug the opening external files in "read-only" ?

Vote
Check!
(thinking…)
Reset
Signed in as (Sign out)
You have left! (?) (thinking…)
• ## Enable step-through debugging in fluent method chains

Fluent syntax is becoming a bigger and bigger part of C# with every release (LINQ and expression-bodied members being two prime examples). However, the debugging experience for fluent syntax is absolutely terrible. If I have a method chain like this

var result = mySource
.Foo(x, y)
.Bar(z)
.Baz();

and I need to examine the intermediate result of Foo that is passed to Bar while debugging, I must refactor my code into a more imperative syntax:

var temp1 = mySource.Foo(x, y);
var temp2 = temp1.Bar(z);
var result = temp2.Baz();

The same applies to expression-bodied members, which must be converted back to…

Vote
Check!
(thinking…)
Reset
Signed in as (Sign out)
You have left! (?) (thinking…)
• ## Let the user have the ability to turn off the auto horizontal scroll. It is very counterproductive to auto ignore the tab indentations!

Just give the user the ability to turn this odd functionality off! Please!

Vote
Check!
(thinking…)
Reset
Signed in as (Sign out)
You have left! (?) (thinking…)
• ## Allow debugging of projects whose assembly names differ by configuration

For historical reasons, some projects we develop produce differently-named assemblies depending on the configuration. This is achievable by manually editing the project file to include a new AssemblyName definition for certain configurations.

Visual Studio builds the project correctly for all configurations, and the assembly can be run stand-alone. However, if you attempt to start debugging the project in a configuration in which the assembly name has been overridden, Visual Studio gives the error:

> Visual Studio cannot start debugging because the debug target 'c:\path\to\correct\bin\dir\UnchangedAssemblyName.exe` is missing. Please build the project and retry, or set the OutputPath and AssemblyName properties appropriately…

Vote
Check!
(thinking…)
Reset
Signed in as (Sign out)
You have left! (?) (thinking…)
• ## Continue but temporarily ignore active breakpoints (as in chrome tools)

In chrome debugging tools when halted on a javascript breakpoint you can click the 'resume script execution' button which then continues until the script finishes or until it hits another breakpoint (just like VS debugger behaviour).

If, rather than clicking the button you press and hold it, an option appears which if clicked, continues execution but temporarily ignores any further breakpoints even though the breakpoints are still active.

Maybe VS already has this continue-but-temporarily-ignore behaviour but I haven't found it. If not, I think this would be a great addition to Visual Studio. At the moment if I'm halted on…

Vote
Check!
(thinking…)
Reset
Signed in as (Sign out)
You have left! (?) (thinking…)
• ## List symbols in a module like x command in windbg

In WinDbg, if the pdb symbol of a module is loaded, it can display and search for symbols in the module, by using "x" command. In Visual Studio, it doesn't seem to have this functionality. I hope I am able to do this in Visual Studio too.

Vote
Check!
(thinking…)
Reset
Signed in as (Sign out)
You have left! (?) (thinking…)
• ## Support of parsing DWARF

Support of parsing DWARF information directly, rather than using DWARF-to-PDB scripts. Very helpful when debugging binaries produced with any kinds of MinGW compilers

Vote
Check!
(thinking…)
Reset
Signed in as (Sign out)
You have left! (?) (thinking…)
• ## When debugging a UWP app and an uncaught exception is thrown, the debugger should break at the location from which the exception is thrown

If you create a new WinForms project and add a single line in the constructor of Form1.cs:
throw new Exception();

Then hit F5. The exception is uncaught and the debugger breaks at that line.

If you create a UWP project and add a single line to the constructor in MainPage.xaml.cs:
throw new Exception();

It breaks in the UnhandledException default handler in App.g.cs.

Can you bring back the developer-friendly feature of breaking right where the exception is thrown? When developing for UWP, it makes it much more difficult and time consuming to find even the simplest bugs (ex. null ref exception)…

Vote
Check!
(thinking…)
Reset
Signed in as (Sign out)
You have left! (?) (thinking…)
• ## Add ability to filter disabled exceptions

I like the new Exceptions Settings window. Current filter functionality only allows you to show the enabled exceptions. For me, I'm often wondering what exceptions I've excluded, wanting to turn them back on.

Vote
Check!
(thinking…)
Reset
Signed in as (Sign out)
You have left! (?) (thinking…)
• ## Support breakpoints conditional on other breakpoints being hit

In XCode, you can (as far as I remember) make a breakpoint that is conditioned on another breakpoint's hit count. This would be extremely useful for reproducing bugs that hit the same place several times, but only one of those times, which occurs after a certain other thing, is actually interesting.

Vote
Check!
(thinking…)
Reset
Signed in as (Sign out)
You have left! (?) (thinking…)
• ## Stop using MS Edge for debugging ASP.Net apps

Positing for a second that MS Edge is unsuitable for debugging ASP.Net apps (see list below), PLEASE stop defaulting to that browser when debugging. I prefer to have the experience relatively streamlined so that I can focus on debugging *my* code. However, with Edge's flakiness, I'm having to jump debugging paradigms and deal with whatever bugs Edge wants to expose. It's just a royal pain in the &*# compared to vPrev, which wasn't great for ASP.Net either.
Why Edge is bad for debugging ASP.Net:
1. VS does not attach its debugger; it uses Edge's, so I constantly have to open…

Vote