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. Add Higher Order Generics to F# (Type Classes)

    Add ability to remove code duplication in F# by allowing to abstract over the container type 'M 'a.

    620 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    17 comments  ·  Languages - F# Tools  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for the feedback, but we are not currently planning to add this feature, in part because it would require significant changes to the CLR. In order to acheive the same effect, you could use an encoding like the one that Steffen suggested below. We don’t plan to add syntactic sugar for that encoding, however.

  2. Make Entity Framework Fully Mockable and injectable

    In general, mocking out the Entity Framework DAL is a big pain to accomplish. ObjectContext has no interface and the T4 templates aren't written to create interfaces for the objects they create.

    This hampers good unit testing and makes them less injectable.

    Put an interface on ObjectContext. Have the T4 Templates put interfaces around all of the objects that are generated and make sure that all objects used have interfaces so that mocking frameworks, like MOQ or Moles & Pex can automatically generate stubs to replace the objects in unit tests so that tests don't need to be tightly coupled…

    507 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  .NET  ·  Flag idea as inappropriate…  ·  Admin →
  3. Keep WP7.1 and XNA/WP app development in Visual Studio 2013

    In the first preview version of Visual Studio 2013 it's no longer possible to develop apps for WP7.1 or XNA WP apps (WP8 works fine). Please keep this platform supported in this new version of Visual Studio, thanks.

    475 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  Mobile App Development  ·  Flag idea as inappropriate…  ·  Admin →

    With each release of Visual Studio, we re-assess the feature set we offer.
    Visual Studio 2012 supports Windows Phone 7.x development, and offers a free Express edition.
    Visual Studio 2013 and Visual Studio 2015 support Windows Phone 8.x development, and offer free Community editions.
    Visual Studio 2015 supports Windows 10 Universal apps development, and offers a free Community edition. For more information, see https://www.visualstudio.com/vs-2015-product-editions.

    -Paul Chapman
    Visual Studio Program Manager

  4. #region Directive Considered Harmful (was "Get rid of #region")

    My informal analysis concludes that #regions are used for evil 96% of the time.

    430 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    105 comments  ·  Languages - C#  ·  Flag idea as inappropriate…  ·  Admin →

    Hey Scott,

    Thanks for taking the time to make this suggestion. I think every programmer has one or more features in any language which they just hate because they’ve been abused by someone else. I’ve renamed this post to capture that immortalized hatred all programmers share for such evil constructs!

    Having said that, #regions do have valid use 4% of the time to someone (arguably grouping interface implementations within a class?) and even if there weren’t it’s really far too late to remove them (even if we thought they were evil, which we don’t). It simply wouldn’t be responsible to the millions of developers out there who might have #region directives in their code today either intentionally or having inherited them from other developers (at least some of which have passionately argued on this thread below) to break that code now without a pretty darn good reason. As a rule,…

  5. change the new 2012 bowtie icon back to the smooth style

    The sharp-edged icon that came with the Visual Studio 2012 RC is hard to look at, and looks more like a bowtie than an infinity symbol. Please return it to its former glory before releasing RTM.

    430 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    28 comments  ·  User Interface  ·  Flag idea as inappropriate…  ·  Admin →
  6. Do not introduce the curse of #regions to HTML

    In VS2013.4RC you have announced #region support for HTML: http://blogs.msdn.com/b/webdev/archive/2014/10/16/announcing-new-web-features-in-visual-studio-2013-update-4-rc.aspx

    I understand that removing #regions from C#, as previously suggested and declined, would be unreasonable at this late stage (https://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2678342--region-directive-considered-harmful-was-get-rid).

    Let's not introduce this curse to new languages though.

    Regions are a way for mediocre teams to hide ****** code behind a roll-up. They are not a productivity extension. They do not help lift the breadth developers forward.

    https://twitter.com/tathamoddie/status/522887198941515778
    https://twitter.com/shiftkey/status/522885829442957312
    https://twitter.com/jrusbatch/status/522886424421363713
    https://twitter.com/scottgal/status/522887947075342336

    383 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    32 comments  ·  IDE and Editor  ·  Flag idea as inappropriate…  ·  Admin →
  7. Metro development from F# without the need for C# assemblies

    I believe that today it's not possible to create a top-to-bottom F# app that takes advantage of SL/Metro on desktop and Windows Phone. Some degree of support from C# assemblies is still needed. Making it possible to write a 100% F# app of that flavor would be a great improvement. My 2 cents.

    332 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    14 comments  ·  Languages - F# Tools  ·  Flag idea as inappropriate…  ·  Admin →

    We agree that it would be nice to be able to use F# for all parts of an application, but given that there are always bounds on time and resources, features need to be prioritized.

    F# will have support for building Metro applications using portable libraries, as described in Don Syme’s BUILD talk (http://channel9.msdn.com/Events/BUILD/BUILD2011/SAC-904T), but the front-end of the application will have to be written in VB/C#. The primary focus of the upcoming release is on information-rich programming through type providers and query expressions, so we chose to invest as much as possible in those areas, while still enabling core Metro application scenarios. This approach is similar to our Silverlight support.

    Donna Malayeri
    Program Manager, Visual Studio F#

  8. Conditional formating for Lists and DataGrids and Reporting.

    First, congratulations for this product, its an old wish i had. For the completness of this tool, i think its fundamental to have Lists and Datagrid conditional formatting.

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

    Thank you for your suggestion. As we are no longer investing in new features for Silverlight Client, we are going to decline this suggestion. Conditional formatting in the HTML client can easily be accomplished using JavaScript and Cascading Style Sheets.

    Thanks,
    Elizabeth Maher, LightSwitch Team

  9. Support OpenMP 3.0 or 3.1

    Version 3.0, released in May, 2008. Included in the new features, including tasks, better support for loop parallelism and nested parallelism. These new features are summarized in Appendix F of the OpenMP 3.0 specifications (http://www.openmp.org/mp-documents/spec30.pdf).

    Version 3.1 (http://www.openmp.org/mp-documents/OpenMP3.1.pdf) of the OpenMP specification was released July 9, 2011.

    284 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Languages - C++  ·  Flag idea as inappropriate…  ·  Admin →
  10. Bring back the Visual Studio Achievements extension.

    Greetings,

    For Visual Studio 2010 and Visual Studio 2012 is the achievements extension released. For those who are not familiar with it, I added the links to them below.

    Sadly is this extensions nowhere to be found for Visual Studio 2013. It's not a killing extensions but it sure adds a lot of fun between developers in a company or for students on Facebook. I personally think that it is improving the working environment.

    It would be nice to have this extensions continued or open sourced so the community can work on it.

    Extension for 2010: http://visualstudiogallery.msdn.microsoft.com/ed9e23e2-ff50-43e3-9aa6-c91f27bd6a6d
    Extension for 2012: …

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

    We considered this seriously, and went back to find the old code – but after further investigation, we think it’s time to retire this old extension gracefully. We love the idea of challenges that encourage developers to try out new features in Visual Studio – but rather than bringing back what we had, we’ll probably try something a little different next time. Thanks so much for the great idea!

  11. xUnit should be the default test framework for VS templates

    xUnit is a more powerful and extensible test framework. .NET Core, and ASP.NET 5 use it as their default. xUnit also supports all current platforms .NET does, including Xamarin.

    The default test framework for the Unit Test projects in VS should change to xUnit.

    257 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 →

    xUnit.net Test Project template is available on the Visual Studio Code Gallery.
    Also, the Create Unit Test wizard supports emitting tests in xUnit.net format (using the xUnit.net Test Extensions package).

    Based on the above, I am marking this item declined.

    Pratap Lakshman
    Visual Studio Team

  12. Provide a Visual Studio Express for ARM based tablets like Surface RT

    I was the proud owner of a Microsoft Surface RT and many times I had an Idea I had to first write it down and test it at home when I had my Surface RT with me in the train or in the plane.

    I think there is a big thing missing in the whole RT tablets Idea and that is an IDE to allow developers to develop application for their beloved tablet or phone.

    Let's have a Visual Studio Express version that can be deployed on Surface RT and the like and it can be restricted to developing Universal…

    254 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    34 comments  ·  IDE and Editor  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your feedback. With the upcoming Visual Studio ‘15’ release, we are working hard to make Visual Studio more lightweight and easier to install. However, the system requirements of Visual Studio are incompatible with Windows RT, and we have no plans to port Visual Studio to that Windows edition.

    Paul Chapman
    Visual Studio Program Manager

  13. 249 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    declined  ·  18 comments  ·  Languages - C++  ·  Flag idea as inappropriate…  ·  Admin →
  14. Re-open the "Bring back Classic Visual Basic" suggestion for VB6 Programming

    The "Bring back Classic Visual Basic" suggestion
    http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/3440221-bring-back-classic-visual-basic-an-improved-versi
    should be re-opened to allow voting.

    It has twice been closed, but it was closed without going to review, which is against Microsoft UserVoice policy.

    And this suggestion is by far the most popular on UserVoice judging by the number of comments (over 4300).

    Clearly this issue won't go away, closing this suggestion doesn't close down the demand for VB6 Programming.

    Remember, you claim this site is for "This site is for suggestions and ideas" - yet you close down suggestions you don't like.

    Open the suggestion, and allow voting .

    249 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    89 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Zagor,

    As you mentioned, the suggestion in question was closed. Before it was closed it was reviewed and given due consideration. The result of that consideration, including the final decision is detailed in the response to the linked bug. The duplicate issue you mention was precisely that, a duplicate. It is our policy to merge/close duplicates. This is usually done to merge open ideas and combine their votes and comments but is done for duplicates of closed suggestions as well. Merging is often done promptly and silently though that is not always the case. While we understand that all participants may not be satisfied with our decisions on UserVoice suggestions or the reasons we give for them, creating duplicates or posts suggesting re-opening those suggestions are not an appropriate (or viable) means to re-open consideration.

  15. Language integrated compiler extensibility

    Similar to Boo or Nemerle's syntactic macros, I'd like to be able to tranform and emit F# code during compilation to create new language constructs.

    242 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Languages - F# Tools  ·  Flag idea as inappropriate…  ·  Admin →
  16. The ability to develope and "plug-in" a common module/widget to an existing applicatoin

    The ability to developed LS applications in modules. Most LOB applications start off simple and evolve over time into large systems. The ability to develop smaller modules and link them together would be a great advantage in LS.

    241 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    19 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Frank,

    Thank you for your suggestion. We are declining the suggestion because we are currently focused on Office 365 and HTML support. We will support the Silverlight client for as long as Silverlight is supported but no new innovation will be happening for the Silverlight client. See http://social.msdn.microsoft.com/Forums/vstudio/en-US/7b92697d-ff35-4c04-8ac5-8949870c6c58/lob-html5 for more details on product direction. Creating a custom control for the HTML client can be done by setting the control type to Custom Control and using the appropriate JavaScript or JavaScript based control.

    Thanks,
    Elizabeth Maher, LightSwitch Team

  17. Do not eliminate the CLASSIC view of MSDN

    Microsoft is apparently about to eliminate the classic view of MSDN in favor of the poor low-contrast, pale, washed out 'lightweight' view. When you visit MSDN now you will see the following if you are viewing the CLASSIC view:

    "This view of the MSDN and TechNet Libraries will be replaced soon with the Lightweight view. Try it now by clicking the Lightweight link above."

    This is more of the same from Microsoft in reducing the developer experience to a shred of what it once was, and makes using MSDN as unpleasant as the grey theme of VS2012.

    240 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    declined  ·  22 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Bring Silverlight Back-The best product that Microsoft ever built

    Microsoft we all know that you are in troubled waters after the surface debacle, Windows-8 also is a major flop. But still we are with you and we can hit back, just bring back one weapon from the junkyard, 'SILVERLIGHT', the best product Microsoft ever built. Work on Silverlight 6 and see how the tables turn. Please bring it back.

    238 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Make AOP a fundamental part of the .NET framework

    Currently there is not satisfactory way of handling cross cutting concerns i.e. tracing. If would be fantastic if aspects could be added to .NET.

    232 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Languages - F# Tools  ·  Flag idea as inappropriate…  ·  Admin →
  20. Create migration tooling for TFS

    As a ALM Consulting I need good migration tooling so that I can push data from one TFS server to another.

    The idea would be to create solid open source tooling that really supports consultants in the field. The TFS Integration Tools are too often a sledge hammer when a scalpel will do and the lack of investment is making them more and more irrelevant. We need to have simple tooling to move work between TFS servers, Collections, and Team Projects which is not currently supported scenarios in the Integration Tools.

    230 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Version Control (Git/TFVC)  ·  Flag idea as inappropriate…  ·  Admin →

Feedback and Knowledge Base