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. Include Pex and Moles with all Visual Studio editions

    Include Pex and Moles with all editions of Visual Studio including Professional edition rather than being restricted to developers with Premium or Ultimate editions of Visual Studio. This will allow all Visual Studio developers to leverage the capabilities of the Moles mocking library and the additional feedback for Unit Testing available with Pex.

    869 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    23 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →

  2. Test Explorer is severely limited

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/351051/test-explorer-is-severely-limited.html
    I have to assume the people who developed the VS2012/2013 test explorer view never actually had to use it in production. The test explorer view is horribly limited in comparison to the one in VS2010.

    1. Running tests does not open the Test Explorer window until after all the tests completed running. There's literally no indication that anything is happening. VS2010 immediately opened the window to show you that the tests were running.

    2. Where are the columns? Most importantly: the error message…

    730 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    started  ·  75 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →

  3. Make IntelliTest available to Visual Studio Professional

    In Visual Studio 2015 IntelliTest are a fantastic idea!
    Restricting it to Visual Studio Ultimate is not a good news. Please make it available to more users.

    681 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    31 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →

  4. Allow Test Explorer To export test results

    When running tests in Test Explorer, there doesn't appear to be a way to export these results. This would be useful in order to share failed test results with fellow team members. Ability to export to trx would be wonderful. I know this can be accomplished via commandline, but running from commandline is a rather clunky solution, especially if you want to re-run failed test.

    513 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    20 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →

  5. Enable IntelliTest to generate tests for VB.NET projects

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/351350/enable-intellitest-to-generate-tests-for-vbnet-pro.html
    Please extend IntelliTest to enable generating tests for VB.NET projects.

    491 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    under review  ·  32 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →

  6. support Spec Explorer in Visual Studio 2013

    Spec Explorer 2010, a model-based testing tool extension is supported in Visual Studio 2010/2012, this suggestion is to make it work with Visual Studio 2013.

    440 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    29 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →

  7. Starting then running all unit tests in a solution can take a very long time.

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/351207/starting-then-running-all-unit-tests-in-a-solution.html
    We have over 200 projects, 2900+ unit tests. It takes over a minute some times to get to the point where it can start listing all the unit tests in the test window, and start executing. We have latest gen Core I7, 8GB 64 bit windows, and it is still a pain. Maybe this area needs 're-imagining', as I can understand the complexities of managing this large number of projects/tests, but it is not working well for us.

    437 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    33 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →

  8. Support Microsoft Fakes on .NET Core

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/351467/support-microsoft-fakes-on-net-core.html
    Microsoft Fakes is powerful function for testing. Please provide support to use Microsoft Fakes Stub/Shim context in .NET Core test project.

    367 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    8 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →

  9. Replace Action Recordings in MTM with Xamarin Test Recorder

    Action Recordings (https://msdn.microsoft.com/en-us/library/dd286647(v=vs.110).aspx) are nearly useless and are very fragile. Instead Xamarin Test Recorder https://www.xamarin.com/test-cloud/recorder should be integrated into MTM (Microsoft Test Manager) and extended to work with WPF/Win Form/ Desktop applications that require automated testing.

    366 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    6 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →

  10. Make the VS Test Explorer Open source

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/351507/make-the-vs-test-explorer-open-source.html
    This entry tracks the interest in seeing the VS Test Explorer open sourced.

    317 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    9 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →

  11. Add option to control automatic test discovery after builds

    I am working on solution that contains 13 000+ unit tests split between several (10+) projects. I am trying to use TDD, but after each build there is a long time window while Test Explorer tries to discover ALL the tests in my solution.
    I need an option to disable/enable the automatic test discovery and a new command to trigger it manually whenever I need to refresh the test list. This will save me literally hours each day.

    284 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    9 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →
    AdminVisual Studio Team (Product Team, Microsoft Visual Studio) responded

    As explained in this blog post (http://blogs.msdn.com/b/visualstudioalm/archive/2015/10/08/how-we-use-user-voice-to-make-a-better-product.aspx), we had updated the status of this suggestion to “Under Review” to let you know we are tracking it on our backlog. To better indicate which one we are actively working on or which ones are on our 6-month plan, we introduced the states “Started” and “Planned”. The goal is to give an update on in progress suggestions at least every 3 months. This suggestion is still on our backlog, but they are not part of the 6-month plan.

    Ewald Hofman

  12. Coded UI test html log should record assertion

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/351344/coded-ui-test-html-log-should-record-assertion.html
    Include assertion checks in the HTML log file created by QTAgent this is essential for testers as many times they are asked to show proof specially in medical companies(at list that what my personal experience says)

    272 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    6 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →

  13. Code coverage support for Windows Phone projects

    Please enable code coverage support for Windows Phone projects.

    259 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →

  14. Enable ordered test support for MSTest V2 framework based tests

    Enable ordered test support for MSTest V2 framework based tests.

    252 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    7 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →

  15. Enable IntelliTest to generate tests for .NET Core projects

    Please extend IntelliTest to generate tests for .NET Core projects.

    238 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    7 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →

  16. Code Coverage support for Windows Store Applications (Windows 8 Apps)

    Please enable code coverage support for Windows Store Applications (Windows 8 Apps).

    232 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    7 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →

  17. Coded UI support in multi desktop feature of Windows 10

    Hi,

    I have installed latest Windows 10 and Visual Studio 2013 Update 5.

    Initiated a Run CodedUI test in Windows 10 -> Desktop 1, opened Desktop 2 to do some other work and hoping that CodedUI test will run in Desktop 1.

    But my assumption was wrong.

    Visual Studio is Running on Desktop 1.

    Execution of opening Web browser and Navigating took place in Desktop 2.

    Where I thought still both Desktop 1 and Desktop 2 are active sessions, hence CodedUI execution would be take place in Desktop 1.

    Is it a bug or behavior is correct.

    As a end…

    225 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    6 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →

  18. Support Spec Explorer in Visual Studio 2015

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/351408/support-spec-explorer-in-visual-studio-2015.html
    Spec Explorer is a masterpiece for testing requirements:
    It is closest to the best general known way of defining requirements ( thanks to abstract state machines) in a language you master using a very rich object-object oriented architecture!
    Please make it work with Visual Studio 2015.

    223 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    under review  ·  11 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →

  19. Enable IntelliTest for 64 bit projects

    Enable IntelliTest for 64 bit projects

    203 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    13 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →

  20. The Processor Architecture for Tests should use the current Platform type

    1. Pick a Platform and Configuration from the drop-downs
    2. Go to Test Explorer and run tests

    All tests FAIL!

    The tests use the 'Default Processor Architecture' which can be configured under the TEST menu. If that doesn't match the Platform type I'm working with, tests fail to run.

    Whenever I change the Platform, I need to remember to also change the Default Processor Architecture.

    I suggest that when I pick a platform, the Default Processor Architecture also changes to match.

    203 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    3 comments  ·  Test Tools  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 … 20 21

Visual Studio IDE

Feedback and Knowledge Base

(thinking…)