Visual Studio IDE

Announcement: This forum has been migrated to provide our customers one convenient and responsive system for all feedback. You can now suggest new ideas, browse and vote on existing ideas in the Visual Studio Developer Community. To learn more about the migration to Visual Studio Developer Community please check out the release blog post.

We’d like your suggestions and ideas to help us continuously improve future releases of Visual Studio, so we’ve partnered with UserVoice, a third-party service, to collect your feedback. Please do not send any novel or patentable ideas, copyrighted materials, samples or demos for which you do not want to grant a license to Microsoft.

This site is for feature suggestions; if you need to file a bug, you can visit our Developer Community website to get started.

Note: your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy and license terms.

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. Allow the evaluation of lambda expressions while debugging

    Allow Quick Watch and other Debug functions to work with Lambda expressions.

    "Expression cannot contain lambda expressions" makes this powerful language feature second-class within the IDE.

    Especially for data intensive applications being able to write Lambda expressions in the Quick Watch, Watch, Immediate Windows and debug evaluation is a must have.

    9,338 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    99 comments  ·  Debugging and Diagnostics  ·  Flag idea as inappropriate…  ·  Admin →

    Hi,

    This suggestion is complete. You can now debug lambda expression starting with Visual Studio 2015 Preview http://www.visualstudio.com/en-us/downloads/visual-studio-2015-downloads-vs

    For more information, please, read: Support for debugging lambda expressions with Visual Studio 2015
    http://blogs.msdn.com/b/visualstudioalm/archive/2014/11/12/support-for-debugging-lambda-expressions-with-visual-studio-2015.aspx

    We are currently working on edit and continue support for Lambdas. I can’t give you an exact time frame as we are quality driven, but we’ll ship it as soon as it is ready so please keep following our 2015 announcements.
    There will also be an update on the related UserVoice item: https://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/4079440-edit-continue-allow-the-modification-of-lambda

    If you have any feedback or questions for us, please, reach out through:
    Send-a-Smile (Visual Studio feedback tool)
    https://twitter.com/VS_Debugger
    vsdbgfb@microsoft.com
    commenting on the blog post

    If you would like to follow news about the Visual Studio Debugger, please subscribe to our blog or to our twitter account.

    Thanks for sharing this suggestion with us and for using Visual Studio!
    Maria Ghiondea
    Visual Studio Diagnostics

  2. Edit & Continue: Allow the modification of lambdas and anonymous methods

    This has been split from https://visualstudio.uservoice.com/admin/forums/121579-visual-studio/suggestions/2035769-make-edit-and-continue-work-more-globally.

    Edit and Continue has always been a staple of Visual Studio development; it's one of the most important features that make it better than other IDEs. In 2002, Visual Studio .Net came out, and didn't have Edit and Continue, which made it very hard to use. In 2003, the new version had Edit and Continue and I was jubilant.

    Enable edit and continue for lambda changes; that might mean that you even have to allow edit and continue to add new methods, but that should be possible using light-weight code generation.

    (Filed on…

    2,447 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Debugging and Diagnostics  ·  Flag idea as inappropriate…  ·  Admin →

    A preview of edit and continue support for Lambda expressions is available in the Visual Studio 2015 RC release (see http://blogs.msdn.com/b/visualstudioalm/archive/2015/04/29/net-enc-support-for-lambdas-and-other-improvements-in-visual-studio-2015.aspx). We’re still working through bugs in the capability so we’re not calling it complete yet, but please give it a try and report any problems you encounter with it on the Roslyn GitHub issues page https://github.com/dotnet/roslyn/issues/

    Andrew Hall
    Visual Studio Debugger

  3. x64 edit and continue

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

    1,977 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    102 comments  ·  Debugging and Diagnostics  ·  Flag idea as inappropriate…  ·  Admin →
  4. Provide integrated JavaScript debugging in Firefox and Google Chrome browsers

    Currently, integrated JavaScript debugging with Visual Studio is only possible with Internet Explorer. Even though you can do a bit of JavaScript debugging with external tools in Mozilla Firefox and Google Chrome, the experience for debugging is not nearly as good as the integrated JavaScript debugging experience available with Internet Explorer. However, JavaScript errors often cause the IE browser to crash, thus making it very difficult to provide a great JavaScript debugging experience with Visual Studio. Therefore, Microsoft should provide integrated Visual Studio debugging experiences with Mozilla Firefox and Google Chrome as they are the most popular alternative browsers in…

    1,295 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    32 comments  ·  Debugging and Diagnostics  ·  Flag idea as inappropriate…  ·  Admin →
  5. 1,107 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    61 comments  ·  Debugging and Diagnostics  ·  Flag idea as inappropriate…  ·  Admin →

    Visual Studio 2015 RTM contains support for C++ Edit and Continue for both x86 and x64 with the default debug engine (which means you can use EnC and other features such as natvis and async call stacks at the same time). We’ll continue to improve the experience based on feedback but we believe we have completed this feature to a level that we can close this item. Read more details at http://blogs.msdn.com/b/vcblog/archive/2015/07/22/c-edit-and-continue-in-visual-studio-2015.aspx

    Best Regards,
    Andrew Hall
    Visual Studio Debugger

  6. Function return value in debugger

    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!).

    1,093 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Debugging and Diagnostics  ·  Flag idea as inappropriate…  ·  Admin →
  7. Support JavaScript debugging for Microsoft edge

    Visual Studio should stop debugging when Microsoft Edge is closed. Additionally Visual Studio should be able to debug JavaScript running in the Microsoft Edge browser.

    880 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    32 comments  ·  Debugging and Diagnostics  ·  Flag idea as inappropriate…  ·  Admin →
  8. Debugger should support authentication with SourceLink

    The C# compiler and the debugger currently support a '/SourceLink' which is a technology where the compiler can emit a JSON file telling the debugger how to locate source files. See https://github.com/dotnet/core/blob/master/Documentation/diagnostics/source_link.md for documentation.

    This works great for public projects on GitHub, or other sites that don't require authentication. But the debugger doesn't yet support hosts that require authentication.

    562 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    16 comments  ·  Debugging and Diagnostics  ·  Flag idea as inappropriate…  ·  Admin →

    I’m excited to let everybody know that the VS Debugger now supports Authenticated Source Link for VSTS and GitHub starting in 15.7 Preview 3: https://blogs.msdn.microsoft.com/visualstudio/2018/04/09/visual-studio-2017-version-15-7-preview-3/

    From the blog post:
    Source Link Authentication: The debugger now supports authenticated Source Link requests for Visual Studio Team Services and private GitHub repositories. When debugging code that was built on another computer, such as a library in a NuGet package, Source Link enables the debugger to show correctly matching source code by downloading it from the internet. To build your own code with Source Link enabled see https://aka.ms/SourceLinkSpec.
    For VSTS repositories, authentication is provided by signing into Visual Studio. For GitHub, we leverage credentials from the GitHub Extension for Visual Studio and the Git Credential Manager for Windows. If Source Link fails due to an authentication error a new “Source Link Authentication Failed” page is shown to explain the issue. This page allows…

  9. Debugger should support C# compiler '/embed' option

    The C# compiler supports embedding sources files into the PDB via the '/embed' option. However, currently the debugger will not automatically pull them back out and show them. This item tracks properly supporting this feature in the debugger.

    307 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Debugging and Diagnostics  ·  Flag idea as inappropriate…  ·  Admin →
  10. .NetCore Code Metrics

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/351625/netcore-code-metrics.html
    Make the Code Metrics feature and command line power tool work against projects/binaries that target .NetCore.

    287 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  Debugging and Diagnostics  ·  Flag idea as inappropriate…  ·  Admin →
  11. Update image watch for 2017

    The Image Watch plugin is an invaluable tool for developing image processing functions. Please make this component work for VS2017.

    271 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Debugging and Diagnostics  ·  Flag idea as inappropriate…  ·  Admin →
  12. Please update Visual Studio Metrics Power tool to support VS2012 and FxCop 11

    The Metrics Power Tool for Visual Studio 2010 is not compatible with the version of FxCop that ships with Visual Studio 2012. It looks like the interface changes that cause the break are minimal.

    We use the Metrics Power tool in our build process and derive a number of reports from the data gathered during the nightly builds.

    Please release an updated version of the Metrics Power tool which works with FxCop 11 or release an updated installer of the powertool that includes the correct dependencies so that it can be used without having to install Visual Studio 2010 alongside…

    222 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    13 comments  ·  Debugging and Diagnostics  ·  Flag idea as inappropriate…  ·  Admin →
  13. Properly support native thread naming via the SetThreadDescription API in minidumps, debuggers, and analysis tools

    This is a request to embed support for the SetThreadDescription API to critical Microsoft debugging and analysis tools: the Visual Studio Debugger, WinDbg, WPA, and mini-dumps.

    A different User Voice request, titled "Add a thread name property for native threads to support attach and minidump debugging" was recently closed, with the rationale that Microsoft was working on a new approach to thread naming. This approach would be different from the current exception-based approach, and "[Microsoft] will look to leverage that in the future for any investments we make to debugging multithreaded code."

    https://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/5792677-include-and-use-native-thread-names-in-minidumps

    From the following conversation I had with…

    220 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Debugging and Diagnostics  ·  Flag idea as inappropriate…  ·  Admin →
  14. Attach child process to debugger automatically

    Visual Studio debugger should support automatically debugging created child processes

    183 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Debugging and Diagnostics  ·  Flag idea as inappropriate…  ·  Admin →

    Hi,

    This suggestion is complete.

    For more information, please, read: Introducing the Child Process Debugging Power Tool
    http://blogs.msdn.com/b/visualstudioalm/archive/2014/11/24/introducing-the-child-process-debugging-power-tool.aspx

    If you have any feedback or questions for us, please, reach out through:
    Send-a-Smile (Visual Studio feedback tool)
    https://twitter.com/VS_Debugger
    vsdbgfb@microsoft.com
    commenting on the blog post

    If you would like to follow news about the Visual Studio Debugger, please subscribe to our blog or to our twitter account.

    Thanks for sharing this suggestion with us and for using Visual Studio!
    Maria Ghiondea
    Visual Studio Diagnostics

  15. Setting breakpoints on auto-implemented properties

    Often times I am motivated to create properties that have no custom accessor or specifier bodies. For example:

    class Person
    {
    private int _age { get; set; }
    }

    The advantage of a property over field in this case is that if I ever want to debug how and when _age is being mutated or accessed I can fill in the bodies of get and set with an obligatory backing field:

    class Person
    {
    private int _ageBacking;

    private int _age { get { return _ageBacking; } set { _ageBacking = value; }
    }

    and set breakpoints in the get and…

    137 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Debugging and Diagnostics  ·  Flag idea as inappropriate…  ·  Admin →

    Hi,

    You can now do this with Visual Studio 2015 Preview http://www.visualstudio.com/en-us/downloads/visual-studio-2015-downloads-vs

    Please see our blog post for more details: http://blogs.msdn.com/b/visualstudioalm/archive/2014/11/14/set-breakpoints-on-auto-implemented-properties-with-visual-studio-2015.aspx

    If you have any feedback or questions for us, please, reach out through:
    Send-a-Smile (Visual Studio feedback tool)
    https://twitter.com/VS_Debugger
    vsdbgfb@microsoft.com
    commenting on our blog post – http://blogs.msdn.com/b/visualstudioalm/archive/tags/diagnostics/

    If you would like to follow news about the Visual Studio Debugger, please subscribe to our blog or to our twitter account.

    Thanks for sharing this suggestion with us and for using Visual Studio!
    Maria Ghiondea
    Visual Studio Diagnostics

  16. Improve the Debug, Exceptions dialog

    The Debug, Exceptions dialog is very painful right now.

    Here are some suggestions for improvement:

    The checkboxes should be on the left, so that they're easier to line up to the text.

    It should have a filter/search box.
    It should handle the space key to toggle the selected row.
    It should support multi-select (see above)
    It should be resizable.

    108 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Debugging and Diagnostics  ·  Flag idea as inappropriate…  ·  Admin →

    Hi,

    This suggestion is now complete, starting with Visual Studio 2015 CTP 6: http://blogs.msdn.com/b/visualstudio/archive/2015/02/23/visual-studio-2015-ctp-6-and-team-foundation-server-2015-ctp-released.aspx

    For more information, please, read: http://blogs.msdn.com/b/visualstudioalm/archive/2015/02/23/the-new-exception-settings-window-in-visual-studio-2015.aspx

    The second part of this suggestion (profiles) is covered by: http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3352678

    If you have any feedback or questions for us, please, reach out through:
    Send-a-Smile (Visual Studio feedback tool)
    https://twitter.com/VS_Debugger
    vsdbgfb@microsoft.com
    commenting on the blog post

    If you would like to follow news about the Visual Studio Debugger, please subscribe to our blog or to our twitter account.

    Thanks for sharing this suggestion with us and for using Visual Studio!
    Maria Ghiondea
    Visual Studio Diagnostics

  17. Improve Usability of the Exception Dialog

    In editions prior to Visual Studio 2010, exceptions were handled by breaking on the line that threw the exception and displaying the Exception Assistant, a dialog that was non-modal and non-distracting.

    In more recent editions, this feature has been removed, returning to a large, obscuring modal dialog. Dismissing this dialog on every exception is painful, frustrating and a usability issue.

    I would prefer the Exception Assistant was included in Express regardless, but given that it was removed for valid reasons (large number of dependencies, as mentioned on Microsoft Connect), I would suggest the following usability requirements as a *bare minimum*…

    107 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Debugging and Diagnostics  ·  Flag idea as inappropriate…  ·  Admin →
  18. Support for source maps

    The TypeScript team build support for source maps into the TypeScript compiler. It would be great if Visual Studio would support this. This would allow a developer to debug TypeScript as TypeScript and not as JavaScript.

    Please check:
    http://www.aaron-powell.com/web/typescript-source-maps
    http://www.html5rocks.com/en/tutorials/developertools/sourcemaps/

    107 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Debugging and Diagnostics  ·  Flag idea as inappropriate…  ·  Admin →
  19. We need a 64 bit of VS, If 32 bit VS debugging performance for 64 bit app cannot be improved.

    64 bit had become popular for a long time. We all need it. Debugging is very important for each developer. We debugging many many times each day, we cannot suffer from the poor performance of remote debugger simulation (MSVSMON.exe) even we are debugging a local 64bit app.

    82 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Debugging and Diagnostics  ·  Flag idea as inappropriate…  ·  Admin →
  20. Shows the Ctrl+Alt+E exception dialog instantly

    On my laptop/sln Showing the Ctrl+Alt+E exception dialog takes around 6s in VS2010, 4s in VS2008 and 2s in dev11DeveloperPreview (even faster would be great).

    81 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Debugging and Diagnostics  ·  Flag idea as inappropriate…  ·  Admin →

    Hi,

    This suggestion is now complete with Visual Studio 2015 CTP 6: http://blogs.msdn.com/b/visualstudio/archive/2015/02/23/visual-studio-2015-ctp-6-and-team-foundation-server-2015-ctp-released.aspx

    For more information, please, read: http://blogs.msdn.com/b/visualstudioalm/archive/2015/02/23/the-new-exception-settings-window-in-visual-studio-2015.aspx

    If you have any feedback or questions for us, please, reach out through:
    Send-a-Smile (Visual Studio feedback tool)
    https://twitter.com/VS_Debugger
    vsdbgfb@microsoft.com
    commenting on the blog post

    If you would like to follow news about the Visual Studio Debugger, please subscribe to our blog or to our twitter account.

    Thanks for sharing this suggestion with us and for using Visual Studio!
    Maria Ghiondea
    Visual Studio Diagnostics

← Previous 1 3

Feedback and Knowledge Base