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. give me a way to flush the MSBuild targets cache

    In Visual Studio 2010, targets files used in the building of a solution are cached by the IDE and there is no obvious way to flush the cache other than restarting Visual Studio as a whole.

    This means that if you are customizing your build process in a modular fashion with targets files, you're forced to restart the whole IDE before any changes take effect. This makes using Visual Studio to customize your build process very inefficient and discourages good practice of packaging reusable portions of a build process into targets files.

    Please remedy this by either giving us the…

    97 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      3 comments  ·  Project  ·  Flag idea as inappropriate…  ·  Admin →

      Thanks for taking the time to share this suggestion. This item has been around for a couple of versions of Visual Studio and we haven’t acted on it. Looking at the VS “15” plans, we’re not going to take action on this item, so we’re going to close it. If the suggestion is still relevant, please either take a look to see if there’s another suggestion that’s similar that you can vote on, or open a new suggestion.

      - The Visual Studio Team

    • Allow assembly references to switch based on configuration

      This works already for project references but not file references. Reference debug locations in debug build, release locations in release build.

      86 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        7 comments  ·  Project  ·  Flag idea as inappropriate…  ·  Admin →

        Thanks for taking the time to share this suggestion. This item has been around for a couple of versions of Visual Studio and we haven’t acted on it. Looking at the VS “15” plans, we’re not going to take action on this item, so we’re going to close it. If the suggestion is still relevant, please either take a look to see if there’s another suggestion that’s similar that you can vote on, or open a new suggestion.

        - The Visual Studio Team

      • Add project references automatically

        If we have a large solution and type class name which is situated in another assembly and current assembly doesn't have direct reference on it then reference should be added automatically.
        It will be nice to have such possibility.

        75 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          4 comments  ·  Project  ·  Flag idea as inappropriate…  ·  Admin →

          Thanks for taking the time to share this suggestion. This item has been around for a couple of versions of Visual Studio and we haven’t acted on it. Looking at the VS “15” plans, we’re not going to take action on this item, so we’re going to close it. If the suggestion is still relevant, please either take a look to see if there’s another suggestion that’s similar that you can vote on, or open a new suggestion.

          - The Visual Studio Team

        • Allow a project file to be edited without unloading first

          I should be able to edit the MSBuild xml of a project file (eg *.csproj) in the Visual Studio xml text editor without first unloading the project. Visual Studio copes fine if the project file changes by getting a new version from source control or using an external application to edit the file so this limitation seems artificially restrictive.

          72 votes
          Vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            Signed in as (Sign out)
            You have left! (?) (thinking…)
            6 comments  ·  Project  ·  Flag idea as inappropriate…  ·  Admin →

            Thanks for taking the time to share this suggestion. This item has been around for a couple of versions of Visual Studio and we haven’t acted on it. Looking at the VS “15” plans, we’re not going to take action on this item, so we’re going to close it. If the suggestion is still relevant, please either take a look to see if there’s another suggestion that’s similar that you can vote on, or open a new suggestion.

            - The Visual Studio Team

          • Add the ability to set a Project's root directory

            Sometimes I want to organize my C++ project so that the source code is not directly underneath my project folder. For example:

            /ide/MyProject.vcxproj
            /src/MySource.cpp

            When I click "Show All Files" in Solution Explorer it only shows the files that are under the /ide directory. I want to be able to configure this to show the files under the /src directory instead.

            If I attempt to manually add files to the project, then the directory structure under /src is not displayed in Solution Explorer.

            I want to be able to specify the root directory of my source code, and to show…

            71 votes
            Vote
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)
              You have left! (?) (thinking…)
              1 comment  ·  Project  ·  Flag idea as inappropriate…  ·  Admin →

              Thanks for taking the time to share this suggestion. This item has been around for a couple of versions of Visual Studio and we haven’t acted on it. Looking at the VS “15” plans, we’re not going to take action on this item, so we’re going to close it. If the suggestion is still relevant, please either take a look to see if there’s another suggestion that’s similar that you can vote on, or open a new suggestion.
              - The Visual Studio Team

            • Show project vs. DLL vs. GAC and Copy-Local differences in references visually

              It would be useful to be able to tell at a glance which references within a project (in solution explorer, project, references tree) are project references, which are DLL references, and which are GAC references. It would further be worth knowing which ones have Copy Local set to true. This would provide useful information to developers as they make deployments, and would help reduce or eliminate a large class of deployment bugs.

              69 votes
              Vote
              Sign in
              Check!
              (thinking…)
              Reset
              or sign in with
              • facebook
              • google
                Password icon
                Signed in as (Sign out)
                You have left! (?) (thinking…)
                5 comments  ·  Project  ·  Flag idea as inappropriate…  ·  Admin →

                Thanks for taking the time to share this suggestion. This item has been around for a couple of versions of Visual Studio and we haven’t acted on it. Looking at the VS “15” plans, we’re not going to take action on this item, so we’re going to close it. If the suggestion is still relevant, please either take a look to see if there’s another suggestion that’s similar that you can vote on, or open a new suggestion.

                - The Visual Studio Team

              • Integrate Project Linker to solve the Multi-targetting

                Integrate and extend the Project Linker extension to solve the problem of solution with multiple targeting (WPF - Silverlight - WP7 - WinRT...), for example loading only the solution's projects of the target selected, instead of all (in our case we have a solution with more than 140 project).

                69 votes
                Vote
                Sign in
                Check!
                (thinking…)
                Reset
                or sign in with
                • facebook
                • google
                  Password icon
                  Signed in as (Sign out)
                  You have left! (?) (thinking…)
                  0 comments  ·  Project  ·  Flag idea as inappropriate…  ·  Admin →

                  Thanks for taking the time to share this suggestion. This item has been around for a couple of versions of Visual Studio and we haven’t acted on it. Looking at the VS “15” plans, we’re not going to take action on this item, so we’re going to close it. If the suggestion is still relevant, please either take a look to see if there’s another suggestion that’s similar that you can vote on, or open a new suggestion.

                  - The Visual Studio Team

                • Make it easier to work with CopyLocal=False on references

                  If you have a large solution (ours has 30 projects) where some or all of the projects reference multiple assemblies that aren't in the GAC then by default Visual Studio ends up copying all of those referenced assemblies around a LOT during a build. Setting CopyLocal to False on all the references stops them getting copied around, but then you need to come up with another way of getting them all into the output folder so that you can debug, run unit tests, etc.

                  It would be nice to have an easy to select build option that worked back along…

                  65 votes
                  Vote
                  Sign in
                  Check!
                  (thinking…)
                  Reset
                  or sign in with
                  • facebook
                  • google
                    Password icon
                    Signed in as (Sign out)
                    You have left! (?) (thinking…)
                    8 comments  ·  Project  ·  Flag idea as inappropriate…  ·  Admin →

                    Thanks for taking the time to share this suggestion. This item has been around for a couple of versions of Visual Studio and we haven’t acted on it. Looking at the VS “15” plans, we’re not going to take action on this item, so we’re going to close it. If the suggestion is still relevant, please either take a look to see if there’s another suggestion that’s similar that you can vote on, or open a new suggestion.

                    - The Visual Studio Team

                  • Change the solution format so TFS can perform a better merge.

                    Change the solution format so TFS can perform a better merge.

                    Currently the solution file format is horrible and doesn't allow TFS to perform a decent merge of the .sln files. If two users add two projects on two seperate branches the merge doesn't work well.

                    Remove the number of projects count from the solution as it is not necessary at all.

                    63 votes
                    Vote
                    Sign in
                    Check!
                    (thinking…)
                    Reset
                    or sign in with
                    • facebook
                    • google
                      Password icon
                      Signed in as (Sign out)
                      You have left! (?) (thinking…)
                      4 comments  ·  Project  ·  Flag idea as inappropriate…  ·  Admin →

                      Thanks for taking the time to share this suggestion. This item has been around for a couple of versions of Visual Studio and we haven’t acted on it. Looking at the VS “15” plans, we’re not going to take action on this item, so we’re going to close it. If the suggestion is still relevant, please either take a look to see if there’s another suggestion that’s similar that you can vote on, or open a new suggestion.

                      - The Visual Studio Team

                    • Allow MSBuild to clean and build solutions while open in visual studio

                      On every project we run we use PowerShell to drive build and deployments into our local environments.

                      We call MSBuild.exe from PowerShell but frequently get this error message: "CSC : error CS1606: Assembly signing failed; output may not be signed -- Error signing assembly -- The process cannot access the file because it is being used by another process."

                      The only way to work around this issue is to close visual studio, run our build and deploy scripts and reopen visual studio after.

                      Note: this is not a case that we are running MSBuild and trying to build or debug…

                      62 votes
                      Vote
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        Signed in as (Sign out)
                        You have left! (?) (thinking…)
                        3 comments  ·  Project  ·  Flag idea as inappropriate…  ·  Admin →

                        Thanks for taking the time to share this suggestion. This item has been around for a couple of versions of Visual Studio and we haven’t acted on it. Looking at the VS “15” plans, we’re not going to take action on this item, so we’re going to close it. If the suggestion is still relevant, please either take a look to see if there’s another suggestion that’s similar that you can vote on, or open a new suggestion.

                        - The Visual Studio Team

                      • Restore the possibility to remove a linked file from a project under source control without deleting the actual file

                        In VS2008 I could delete a linked file from a project under source control and this would only trigger a pending change for my vbproj file. If I do the same in VS2010 this triggers a pending change for the actual delete of the linked file. This is not how it should work, because I don't want to delete the file, it's still needed in an other project. I just want to remove the link to the file

                        60 votes
                        Vote
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          Signed in as (Sign out)
                          You have left! (?) (thinking…)
                          0 comments  ·  Project  ·  Flag idea as inappropriate…  ·  Admin →

                          Thanks for taking the time to share this suggestion. This item has been around for a couple of versions of Visual Studio and we haven’t acted on it. Looking at the VS “15” plans, we’re not going to take action on this item, so we’re going to close it. If the suggestion is still relevant, please either take a look to see if there’s another suggestion that’s similar that you can vote on, or open a new suggestion.

                          - The Visual Studio Team

                        • Make Configuration Manager faster

                          We have very large solutions with 200+ projects with multiple build configurations (debug/release, x86/x64, additional configurations to build subsets of our applications, etc.) When we need to edit the build configurations, we need to open the Configuration Manager dialog to switch the platform, whether a project is built, etc.

                          1. The dialog should be resizable so we can see as many projects as we have screen real estate for.

                          2. A search/filter like you have added everywhere else in VS11 would be handy

                          3. Most importantly, to work on other configurations, you have to switch the active configuration and platform.…

                          59 votes
                          Vote
                          Sign in
                          Check!
                          (thinking…)
                          Reset
                          or sign in with
                          • facebook
                          • google
                            Password icon
                            Signed in as (Sign out)
                            You have left! (?) (thinking…)
                            1 comment  ·  Project  ·  Flag idea as inappropriate…  ·  Admin →

                            Thanks for taking the time to share this suggestion. This item has been around for a couple of versions of Visual Studio and we haven’t acted on it. Looking at the VS “15” plans, we’re not going to take action on this item, so we’re going to close it. If the suggestion is still relevant, please either take a look to see if there’s another suggestion that’s similar that you can vote on, or open a new suggestion.

                            - The Visual Studio Team

                          • The Properties tab for an assembly reference should also show the assembly's file version

                            In for instance a C# project, if we show the properties of a referenced assembly, the properties list has the element "Version" which currently displays the AssemblyVersion. This element should be renamed "Assembly Version" for clarity. Also, a new element "Assembly File Version" should be added.

                            The motivation for this is that some third party components keep the assembly version constant (i.e. contract version) between minor releases, to reduce need for recompilation of dependent code. Such minor releases will still increase the assembly file version, so that it's possible to distinguish them. Only showing the assembly version in the VS…

                            58 votes
                            Vote
                            Sign in
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              Signed in as (Sign out)
                              You have left! (?) (thinking…)
                              0 comments  ·  Project  ·  Flag idea as inappropriate…  ·  Admin →

                              Thanks for taking the time to share this suggestion. This item has been around for a couple of versions of Visual Studio and we haven’t acted on it. Looking at the VS “15” plans, we’re not going to take action on this item, so we’re going to close it. If the suggestion is still relevant, please either take a look to see if there’s another suggestion that’s similar that you can vote on, or open a new suggestion.
                              - The Visual Studio Team

                            • MSBuild should respect the "Copy Local" setting

                              Often one nuget lib is using other nuget libs(e.g. Microsoft.AspNet.Razor) which may have installed into GAC during the process of installing VS.
                              The dependencies have been set to "Copy Local" = true, but msbuild will not respect this setting if the GAC version is the same as the dependency version. The dll wont be copied but it works fine at local environment. The problem is,
                              very likely, the production server will not install mvc in this case, so when the app tries to start, the dll cant be found. The whole app just will not work at all.
                              If the…

                              51 votes
                              Vote
                              Sign in
                              Check!
                              (thinking…)
                              Reset
                              or sign in with
                              • facebook
                              • google
                                Password icon
                                Signed in as (Sign out)
                                You have left! (?) (thinking…)
                                2 comments  ·  Project  ·  Flag idea as inappropriate…  ·  Admin →

                                Thanks for taking the time to share this suggestion. This item has been around for a couple of versions of Visual Studio and we haven’t acted on it. Looking at the VS “15” plans, we’re not going to take action on this item, so we’re going to close it. If the suggestion is still relevant, please either take a look to see if there’s another suggestion that’s similar that you can vote on, or open a new suggestion.
                                - The Visual Studio Team

                              • Create a Solution Items Folder for dependencies

                                Solution folders are handy for organizing (and sometimes hiding) projects in complex solutions. For this usage, it makes sense that the Solution Folders aren't required to map to physical folders. Another important use is for solution level dependencies: external assemblies referenced by multiple projects, documentation, key files, and such.

                                The biggest reason I hear from developers for not putting these items in a solution folder is that the physical folder mapping is a mess. Most of these developers advocate for adding a "Dependencies" class library project and marking it to not build.

                                Let's just have a container for solution items…

                                47 votes
                                Vote
                                Sign in
                                Check!
                                (thinking…)
                                Reset
                                or sign in with
                                • facebook
                                • google
                                  Password icon
                                  Signed in as (Sign out)
                                  You have left! (?) (thinking…)
                                  1 comment  ·  Project  ·  Flag idea as inappropriate…  ·  Admin →

                                  Thanks for taking the time to share this suggestion. This item has been around for a couple of versions of Visual Studio and we haven’t acted on it. Looking at the VS “15” plans, we’re not going to take action on this item, so we’re going to close it. If the suggestion is still relevant, please either take a look to see if there’s another suggestion that’s similar that you can vote on, or open a new suggestion.

                                  - The Visual Studio Team

                                • Add a switch to MSBuild to force being strict about only building projects in the solution

                                  Currently MSBuild determines all project dependencies and builds those projects regardless of whether they're in the solution being built. This means MSBuild successfully builds the solution but the solution fails to build in Visual Studio.

                                  It would be great to have a switch for MSBuild that would force it to only build the projects in the solution.

                                  Scenario:
                                  The solution AAA.sln has project Foo.csproj which references Bar.csproj (also in the solution). Bar.csproj lives in another solution (BBB.sln) and was modified by a developer to now reference BarHelper.csproj. The developer checked in the changes to BBB.sln but didn’t realise AAA.sln would…

                                  43 votes
                                  Vote
                                  Sign in
                                  Check!
                                  (thinking…)
                                  Reset
                                  or sign in with
                                  • facebook
                                  • google
                                    Password icon
                                    Signed in as (Sign out)
                                    You have left! (?) (thinking…)
                                    3 comments  ·  Project  ·  Flag idea as inappropriate…  ·  Admin →

                                    Thanks for taking the time to share this suggestion. This item has been around for a couple of versions of Visual Studio and we haven’t acted on it. Looking at the VS “15” plans, we’re not going to take action on this item, so we’re going to close it. If the suggestion is still relevant, please either take a look to see if there’s another suggestion that’s similar that you can vote on, or open a new suggestion.

                                    - The Visual Studio Team

                                  • Support OutputType of .netmodule

                                    .NET claims support for .netmodule, but it's support is abysmal. VS doesn't let you switch to them, and when you do it manually project references fail to resolve. MSBuild doesn't support project references to them either. Even after all that is worked around, Csc.exe itself fails to find extension methods in .netmodules.

                                    41 votes
                                    Vote
                                    Sign in
                                    Check!
                                    (thinking…)
                                    Reset
                                    or sign in with
                                    • facebook
                                    • google
                                      Password icon
                                      Signed in as (Sign out)
                                      You have left! (?) (thinking…)
                                      0 comments  ·  Project  ·  Flag idea as inappropriate…  ·  Admin →

                                      Thanks for taking the time to share this suggestion. This item has been around for a couple of versions of Visual Studio and we haven’t acted on it. Looking at the VS “15” plans, we’re not going to take action on this item, so we’re going to close it. If the suggestion is still relevant, please either take a look to see if there’s another suggestion that’s similar that you can vote on, or open a new suggestion.

                                      - The Visual Studio Team

                                    • The VS 11 Reference Manager should store its size and the width of the columns

                                      The new Reference Manager in VS 11 is great, but I have to resize it and the columns in the assemblies list every time I use it. The reason for that is that we use relatively long assembly names (CompanyName.ProductName.Area.Subarea). This is annoying. Please add code to store the size of the dialog and the size of each column when closing and restore this sizes when opening.

                                      41 votes
                                      Vote
                                      Sign in
                                      Check!
                                      (thinking…)
                                      Reset
                                      or sign in with
                                      • facebook
                                      • google
                                        Password icon
                                        Signed in as (Sign out)
                                        You have left! (?) (thinking…)
                                        5 comments  ·  Project  ·  Flag idea as inappropriate…  ·  Admin →

                                        Thanks for taking the time to share this suggestion. This item has been around for a couple of versions of Visual Studio and we haven’t acted on it. Looking at the VS “15” plans, we’re not going to take action on this item, so we’re going to close it. If the suggestion is still relevant, please either take a look to see if there’s another suggestion that’s similar that you can vote on, or open a new suggestion.

                                        - The Visual Studio Team

                                      • Show references to Nuget packages, not all the .dll's in them

                                        There references show for a project in Solution Explorer shows every dll file. If the dll is from a Nuget package, it would be simpler to list the Nuget package instead.

                                        41 votes
                                        Vote
                                        Sign in
                                        Check!
                                        (thinking…)
                                        Reset
                                        or sign in with
                                        • facebook
                                        • google
                                          Password icon
                                          Signed in as (Sign out)
                                          You have left! (?) (thinking…)
                                          3 comments  ·  Project  ·  Flag idea as inappropriate…  ·  Admin →

                                          Thanks for taking the time to share this suggestion. This item has been around for a couple of versions of Visual Studio and we haven’t acted on it. Looking at the VS “15” plans, we’re not going to take action on this item, so we’re going to close it. If the suggestion is still relevant, please either take a look to see if there’s another suggestion that’s similar that you can vote on, or open a new suggestion.

                                          - The Visual Studio Team

                                        • Improve reference dialog regarding Project and Assembly reference

                                          When adding a new file/assembly reference, VS should detect that this file is output from another project part of my solution and suggest a project reference instead. This will reduce potential problems with multiple platform and configuration builds.

                                          37 votes
                                          Vote
                                          Sign in
                                          Check!
                                          (thinking…)
                                          Reset
                                          or sign in with
                                          • facebook
                                          • google
                                            Password icon
                                            Signed in as (Sign out)
                                            You have left! (?) (thinking…)
                                            1 comment  ·  Project  ·  Flag idea as inappropriate…  ·  Admin →

                                            Thanks for taking the time to share this suggestion. This item has been around for a couple of versions of Visual Studio and we haven’t acted on it. Looking at the VS “15” plans, we’re not going to take action on this item, so we’re going to close it. If the suggestion is still relevant, please either take a look to see if there’s another suggestion that’s similar that you can vote on, or open a new suggestion.

                                            - The Visual Studio Team

                                          ← Previous 1 3 4 5 6 7

                                          Feedback and Knowledge Base