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. Stop treating workarounds as a legitimate alternative to standards compliance

    Particularly in the world of C++, where the delta between what the compiler accepts and what the standard says is quite large, it is common for people to report bugs against the compiler.

    Often, however, these are met with refusals to fix the compiler, and claims that there are workarounds.

    I would love you to change this policy.

    Yes, sometimes there is a zero cost workaround to a particular flaw. But that's not a reason to not fix the bug. I write code that I wish to compile in g++, VC++, and sometimes even clang++. Being forced to avoid standard…

    242 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Languages - C++  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add a compiler warning for C-style casts in C++

    Would it be possible to add a new compiler warning that informs the user when a C-style cast has been used in either native or managed C++?

    Although I'm not too concerned with the casting of basic data types (such as float fValue = (float)nValue;) C-style casting of class pointers that may fall through to a reinterpret_cast<T> are particularly dangerous and also difficult to find in existing source code. A compiler warning would help developers identify such instances without resorting to regex searches across files. Generally speaking if something falls through to a reinterpret cast then it has probably gone…

    160 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    closed  ·  6 comments  ·  Languages - C++  ·  Flag idea as inappropriate…  ·  Admin →
  3. Simplify C++ templates error messages

    Please simplify C++ templates error messages like STLFilt does.

    Things that can be hided:
    * Typedef's unrolling
    * Displaying template default arguments
    * The qualifiers "class", "struct", "__thiscall" and "__cdecl"
    * Shorter names for nested classes

    118 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    closed  ·  2 comments  ·  Languages - C++  ·  Flag idea as inappropriate…  ·  Admin →
  4. Support __int128 on 64-bit platform

    When multiplying two __int64 numbers, the 64-bit cpu provides a 128-bit result but the compiler provides no mean to access the higher part.

    94 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Languages - C++  ·  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

  5. Support 'Committed by pressing the space bar' in C++ intelliSense

    I think it's great that the new beta includes a Completion list for intellisense, and makes it infinitely more usable. However for some bizarre reason it is missing the 'Committed by pressing the space bar' option, which is sorely missed by those of us who have been spoilt by the excellent C# intelliSense.

    It seems such a tiny feature to add, but would be warmly welcomed!

    81 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Languages - C++  ·  Flag idea as inappropriate…  ·  Admin →
  6. Add AddressSanitizer a la Clang.

    Basically instrument allocations, reads and writes to catch memory scribbles at word granularity.

    75 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Languages - C++  ·  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

  7. C11

    C11 support or full C99 support. This is needed to cleanly support cross platform C code on Windows. Visual Studio is the only environment that largely DOES not support constructs that are supported on xcode, gcc, and clang. Please do something about this.

    74 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Languages - C++  ·  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

  8. confirm before rebuild

    Please make Visual Studio prompt to confirm before rebuilding an entire project. "Build" and "Rebuild" are right next to each other in the context menu and it's so easy to accidentally click Rebuild instead of Build and end up killing a bunch of time waiting for a large project to build from scratch. This should be SO easy for you guys to implement; very little of your time could save the rest of the industry thousands of man-hours. Please!

    69 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  Languages - C++  ·  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

  9. support compiling with "utf-8 without bom".

    I am in trouble when developing, because there are many tools that do not support the bom.

    I would be grateful, if you could add the compiler option that you can set default language which used in compiling.

    66 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Languages - C++  ·  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

  10. Fix the reference / hint path issue.

    The number of times I have to go in and manually edit the hint paths to point at our lib folder because VS has 'intelligently' decided that it should point at some other copy of the dll. If I tell it to point at a file, that usually means that I want it to reference that 'exact' file.

    58 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Languages - C++  ·  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

  11. Add std::decimal with ISO/IEC TR 24733 decimal floating-point arithmetic

    The document ISO/IEC TR 24733 specifies extension for the programming language C++ to support decimal floating-point arithmetic. Namely, it defines new type std::decimal.

    It would be very helpful to have this type provided by the C++ Standard Library shipped with Visual C++.

    libstdc++ already defines std::decimal:
    http://gcc.gnu.org/onlinedocs/libstdc++/libstdc++-api-4.5/a01127.html

    57 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Languages - C++  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your suggestion. Right now the MSVC team is focused on better conforming to the C++ Standard. We need to prioritize standardized work above work that is in TRs.

    You can bring in the library from the TR yourself if you need to use it. And you should consider pushing the Standards Committee to address the deficit in the language if you want broad-based compiler support for the TR.

  12. CPU dispatch in C++

    Hello,

    I was wondering when Microsoft will implement a CPU dispatch mechanism in Visual C++ like what Intel, GCC, Clang have done, as a __declspec or a pragma. It appears that it is still not the case in VS2012 U1.

    This would be very useful now AVX processors are roaming. We could write different functions optimized for IA32/SSE2/AVX (or compile with different arch) and a single build (EXE or DLL) will run optimized on several CPUs.

    Thank you.

    - D.

    56 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Languages - C++  ·  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

  13. Bring Debugger Canvas to C++

    Please bring the "Debugger Canvas" from Dev Labs and support C++ debugging. It is a life saver for maintaining and understanding old code as well as very valuable in debugging. Currently going through huge code bases and understanding code path is just by going throgh line by line and source file by file. If we can get the Debugger canvas, it is a bliss. There is a "LOT" of potential for a tool like Debugger Canvas in C++.

    46 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Languages - C++  ·  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

  14. XML comments in C++

    C# has nice support for XML comment. You type /// and your XML document is populated, with the proper parameter names, etc.

    Since VS2010, intellisense has been pretty awesome, so I figure it can't be that hard now to implement the same! The compiler already supports XML comments too!

    45 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Languages - C++  ·  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

  15. Please add Unrestricted Union support (www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2544.pdf)

    Unrestricted unions are valuable in memory constrained environments. They provide an extremely compact and intuitive way to house multiple c++ classes in the same memory.

    43 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Languages - C++  ·  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

  16. Option to automatically collapse all inactive preprocessor blocks

    I suggest that Microsoft add an option to automatically collapse all inactive preprocessor blocks in the Visual Studio/C++ IDE.

    This feature would be extremely easy to implement, and enhance productivity considerably, especially for projects that contain many compilation alternatives.

    This feature appears to be on relatively high demand;
    - http://social.msdn.microsoft.com/Forums/vstudio/en-US/97ad0528-8dd8-44eb-b4b8-ede8fdb3cf61/hide-inactive-preprocessor-block
    - http://stackoverflow.com/questions/9094391/collapse-all-inactive-preprocessor-blocks-in-visual-studio
    - http://stackoverflow.com/questions/17332077/can-i-programmatically-collapse-expand-all-preprocessor-blocks-of-a-certain-name

    Best Regards,

    Richard Baxter

    42 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Languages - C++  ·  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

  17. Extend C++ to treat all warnings as errors except a select few (user specified).

    Being able to treat all warnings except a specific few as errors is a valuable thing. The C# compiler supports this.

    For C++ our only options are:

    1) Turn off the "Treat Warnings As Errors" and then use "Treat Specific Warnings As Errors" to list all warnings we want to treat as errors. The problem with this is that we really want to treat 98% of warnings as errors and only exclude a few and listing those 98% of warnings is painful and we'd be prone to miss some.

    2) Turn on "Treat Warnings As Errors" and then list warnings…

    38 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Languages - C++  ·  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

  18. Interop between the concurrency runtime and the CLR

    Make code that uses the concurrency runtime interoperate with the CLR. Trying to circumvent the limitation using the PIMPL idiom does not work either.

    34 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Languages - C++  ·  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

  19. Release more CRT source header files and code.

    There are a number of .h and .inc files that are referenced by source files in the CRT source but which are not included in the CRT source code, specifically:
    ksamd64.inc
    strchr_sse.inc
    strrchr_sse.inc
    strstr_sse.inc
    coresyslibs.h
    ehassert.h
    ehhooks.h
    ehstate.h
    internal_safecrt.h
    ksarm.h
    kxarm.h
    nowin.h
    pch.h
    rtti.h
    trnsctrl.h
    undname.h
    vcver.h
    vcwininternls.h
    xmm_func.h

    Some of them are referenced by name in MSDN articles, e.g. http://msdn.microsoft.com/en-us/library/ff770587%28v=vs.110%29.aspx references rtti.h by name.
    It would be nice to have these header files so that when reading the CRT source code one doesn't bump into things that are defined or declared in .h files that you cant then go…

    33 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Languages - C++  ·  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

  20. Provide command prompt for v110_xp platform toolset in VS2012

    Recently, VS2012 Update 1 CTP has been released. I've installed the update and tried to use command prompt to build the 3rd-party library (some 3rd-party library uses its build script, for example, boost).

    However, the default SDK environment in command prompt is still using WinSDK 8.0.

    if can, providing the command prompt with the environment same as platform target v110_xp (WinSDK 7.1A) will be better.

    29 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Languages - C++  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 11 12

Feedback and Knowledge Base