Visual Studio IDE

Announcement: Last fall, we migrated this forum to Visual Studio Developer Community to provide you one convenient and responsive system for all feedback. As the final step in the migration, this forum will be closed off completely on June 1st, 2019. We encourage you to visit Visual Studio Developer Community where you can now suggest new ideas, browse and vote on existing ideas, and engage with Visual Studio teams.

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. VSIX should support the user's msbuild extensions path as an install root

    VSIX allows files to be installed into a few directories outside the Visual Studio extensions directory, but they're all under the Visual Studio install directory, and requires admin access to install.

    If the VSIX supports installing files to the user MSBuild extensions path (in the use profile directory), then admin access would not be required to install the VSIX, and the extension could support auto-updating.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  2. Change the link for Discover ways to extend and customize the IDE

    When you click the link 'Discover ways to extend and customize the IDE', this should take you to information about extensibility.

    As it now, you are sent to Visual Studio Marketplace.

    Visual Studio seems to confuse 'Find an extension' with extend and customize the IDE.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  3. extensions and tools without restart

    Now that Visual Studio has made it to version 15 (2017), it would be great to have the ability to install extensions without requiring a restart of Visual Studio. Restarting Visual Studio is time consuming and context switching mentally. It reduces developer productivity.

    8 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  4. Publicly expose API for creating InterlineAdornments

    There exists an API for creating Interline Adornments within Microsoft.VisualStudio.Text.Internal. Please considering moving this to one of the publicly available extensibility assemblies so customers can easily create adornments that exist between lines (similar to CodeLens adornments)

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  5. uninstall extension dialog too long

    Some extensions (like Roslyn Expression Evaluator) have so many dependent extensions that the dialog that displays when accidentally clicking the uinstall option extends beyond the length of the monitor. Since the caption bar cannot be moved off screen it is impossible to get to the bottom to see what option(s) are available. The ESC button won't dismiss the dialog nor anything other than pressing ENTER which seems to trigger the uninstall, by default.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  6. Visual Studio - when linking out to external sites that host extensions, maintain context to the version that matches the IDE.

    I use VS2015, as it's the latest IDE that supports SSDT. When I click a link *within the editor* to an extension - it always lands on a VS2017 splash page, which is incorrect. The link out should include context to land on the extension site that corresponds to the version of the IDE generating the link. This would reduce "friction" in using your tools.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  7. Visual Studio extensions performance score/ranking

    Some plugins slow down Visual Studio.

    The VS team has added a great feature that highlights when an extension slows down VS at startup. What would be even better is if each extension had a performance ranking that is visible before users install an extension. This ranking would be based on how many users have performance problems with the extension (as calculated by VS). This will be an incentive for plugin publishers to fix their extension if it causes performance problems for many users.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  8. support setting a custom logger for msbuild from within visual studio without an extension

    One can implement a custom logger for msbuild (https://msdn.microsoft.com/en-us/library/ms171471.aspx) and supplying it in the /logger parameter.

    This works like a charm when using msbuild from outside of visual studio. Inside of visual studio there is not way to supply a logger to msbuild.

    It can be accomplished by writing a visual studio extension - but this adds an additional hurdle and sometimes is not an option.

    We also don't want to resort to workaround like: http://stackoverflow.com/questions/28733875/can-a-msbuild-custom-logger-be-specified-within-a-project-file/28806181#28806181

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  9. Extension version pinning and revert

    Hello,

    We use quite a lot of extensions in our company and love it!
    But sometimes an extension gets updated and it contains a bug or some other snafu and have to then disable that extension.

    I tried searching for a similar request but I haven't found one so here it goes.

    Could you add version support similar to NuGet packages?
    So that we could for instance be able to install version X of the extension or block version Y from being installed? That way we could revert to a previous version of an extension in case it breaks.

    It…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  10. Enable extension management from a stand alone tool

    I would to view the extensions I have installed and manage them without having to run the full instance of Visual Studio.
    This could be very useful when setting up new machines or after upgrading to a new version of Visual Studio.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  11. When updating a disabled extension, keep it disabled

    When I update a disabled extension, I'd like it to stay disabled. Currently, I have to update it, restart VS, disable it, and restart VS again. It's tedious and time-consuming.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  12. Add a checkbox to the VSIX Installer dialog box to open Visual Studio

    Since it is necessary to close Visual Studio to initiate the installation of extensions I suggest that the VSIX Installer dialog box be modified to enabled reopening Visual Studio after the installation is complete. This could be done with an additional button next to the Close button or a check box to enable the option.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  13. Support changing Visual Studio Color Theme programatically in a VS extension

    Currently you can't change VS Color Theme in a VS extension on the fly. There are some ways to do it, but none of them are really great: changing through the registry requires a restart to take effect; you can also import a settings file, however than can also bring other changes which you don't want.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  14. More freedom in VS isolated Shell

    In Vs 2015 isolated shell we need more freedom to create our site. Like edit the Blank Solution : add folders or oder items, so that you do not need to add thmen everytime if you open a new project. Or let the people pu their own template into the isolated shell.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  15. Develope the Information about VS 2015. especially isolated shell part

    Develope the Information about VS 2015. especially isolated shell part

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  16. Download extensions in the background

    It's very nice that the extension dialog now batches installation.
    However, it's still very annoying to be forced to wait while it downloads the VSIX.
    Can you make it download in the background (and show a progress bar in the corner status area)?
    It'd be fine to block closing the extensions dialog until all downloads finish, but I want to continue browsing extensions during downloads.

    17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  17. Enable reading / writing user-scoped project settings via Workspace APIs

    Currently there seems to be no way for accessing the settings stored in .csproj.user files via the Workspace APIs, so any Visual Studio extension relying on the user settings will have to force a full load of the project to access these settings.

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  18. Open Source the VS Achievements Extension

    As described in https://visualstudio.uservoice.com/forums/121579-visual-studio-ide/suggestions/6048161-bring-back-the-visual-studio-achievements-extensio, the VS team appears to have no intention of updating/rebuilding the achievements extension for current versions of Visual Studio. Perhaps another solution (and one that would provide a learning opportunity to the community) would be to open source the extension so that the project can be maintained (or at the least imitated) outside of Microsoft.

    9 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  19. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  20. Link extension list to user profile

    When user get connected with a new visual studio, settings are set as usual user preferences on previous visual studio machine but extensions are not installed.

    I Suggest to link extensions to user profile so, when user get connected to a new machine, at the end of the visual studio connection, VS asks : Do you want to restore your favorite extensions ?

    Thanks

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Extensibility  ·  Flag idea as inappropriate…  ·  Admin →

Feedback and Knowledge Base