# 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. ## 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…)
• ## 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…)
• ## 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…)
• ## 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…)
• ## 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…)
• ## 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
Check!
(thinking…)
Reset
Signed in as (Sign out)
You have left! (?) (thinking…)
• ## "attach to process" does not remember addresses in no authentication mode

If you have a lot of internal (and regularly changing) systems it's just too cumbersome to create pseudo accounts everywhere just for debugging.

Also for convenience these accounts often don't have passwords anyway, even more insecure than no auth mode.

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…)
• ## A simple option to keep console window of console apps OPEN after it exits.

Please provide a simple way to keep console window of console apps visible *after* it exits. Do not force us to play tricks like getch(), command("pause") and you know what.

Just add a checkbox in Debug options: Keep the \$^&% window open.

Vote
Check!
(thinking…)
Reset
Signed in as (Sign out)
You have left! (?) (thinking…)
• ## Enable muting of breakpoints

IntelliJ has a feature that allows "muting" of all breakpoints. This is different than disabling breakpoints in that it doesn't alter the enabled/disabled state. It just mutes them, where all breakpoints behave as if they are disabled. It is immensely useful and a total time saver.

Vote
Check!
(thinking…)
Reset
Signed in as (Sign out)
You have left! (?) (thinking…)
• ## Provide multiple debug channel output windows

Like the Sony Playstation used to do (or still does?) with the TTY channels, it would be great to be able to specify an output stream / channel for debug / diagnostic text so each channel appears in it's own output window. I do this in engine already, but it would be great to be able to view the channels externally within Visual Studio as well

Vote
Check!
(thinking…)
Reset
Signed in as (Sign out)
You have left! (?) (thinking…)
• ## Visual Studio : hotkey similar to ctrl+F10 but also skip all breakpoints

when I press ctrl+F10 at line A, I just want the program to resume and halt when reach line A. However, if it reaches a breakpoint before reaches line A, it will halt at that breakpoint instead. Whether it could ignore or skip the breakpoint?

For detailed requirement:

Vote
Check!
(thinking…)
Reset
Signed in as (Sign out)
You have left! (?) (thinking…)
• ## Show 2D arrays as tables in debugger

The debugger/inspector should display 2D arrays as tables, not as 1D list.

Ideally I could also select & copy/past rectangular regions of arrays. (For analysis in Excel, etc.)

Vote
Check!
(thinking…)
Reset
Signed in as (Sign out)
You have left! (?) (thinking…)
• ## Display call flow lines in disassembly view

For those of us analysing the odd bit of disassembled code in the course of our jobs (but not enough to warrant using eg. IDA or OllyDbg), it'd be super handy to have graphical display of the potential outcomes of jmp instructions, primarily within the same function; just a line pointing from the j* instruction to the destination would be useful enough so that I don't need to scroll to find the destination offset.

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…)
• ## Binding details in live property explorer

Show the source of a value of property along with binding details + errors if any for the properties.

Vote
Check!
(thinking…)
Reset
Signed in as (Sign out)
You have left! (?) (thinking…)
• ## team foundation 2015 build logs in local time

Current TFS Build Info (start, stop) is in local time. As it should be. However build logs are in UTC time which is very frustrating. These should also be in local time, please!
The number of users which need this must be small and if needed some config option could be given.

Vote