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. Include Code Contracts featuers in all editions of Visual Studio, requiring Ultimate makes this very useful feature useless when working wit

    Include Code Contracts features in all editions of Visual Studio. Requiring Ultimate edition makes this very useful feature useless when working with others who do not have Visual Studio Ultimate.

    As a side note, I talked this feature up at our company from Spec# to the Code Contracts SDK only to be disappointing when we couldn't adopt it in the end because it was exclusive to higher additions of Visual Studio, we currently use Professional.

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

  2. Expose stream position of current element in XmlReader

    XmlReader is supposed to work with large XML documents and thus is able to work with stream based data.

    However, when sending big XML documents through message routing systems (like BizTalk), they frequently get wrapped with additional information that is used for messaging purposes (think SOAP or other XML protocols).

    XmlReader currently has no support to cut out the relevant parts of such documents once they reach their destinations, at least not stream based. One can use ReadInner/OuterXml, but that puts a copy of a potentially multi-GB document into memory - not good.

    If XmlReader would give the position of…

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

  3. Zipping support from .Net

    Could you please include sources of Ionic.zip.utils (under ms pl) to .Net platform and speed up his implementation?

    Zipping+AES Encryption is very popular. And used almost everywhere. Comparing to wrapper of 7-zip compression takes longer in 2 times and with begger size, but API of ionic is very great.

    31 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  .NET  ·  Flag idea as inappropriate…  ·  Admin →

    I want to personally thank you for taking the time to share this suggestion. Since the suggestion you raised has not gathered many votes, the Visual Studio team is prioritizing other suggestions and closing it at this time.

    Additionally, please see https://msdn.microsoft.com/en-us/library/system.io.compression.ziparchive

    If you would like us to reconsider this, please create a new suggestion. Again, thank you for sharing with us!

    Paul Chapman
    Program Manager, Visual Studio

  4. Bring ProgressRing and ProgressIndicator to WPF.

    Since ProgressIndicator is just a style template for ProgressBar, there is no reason it shouldn't be accessible in WPF. However I relies on some new animation classes that are only available for WinRT. I would like the new metro controls available to WPF.

    So we can build Zune like Metro desktop UIs.

    31 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  .NET  ·  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. Improve exception messages

    Many exceptions in .NET still do not contain any context information which makes it hard to understand when some exceptions happens.

    For instance, when a key is already added to a dictionary you throw with the message

    "An item with the same key has already been added."

    that message does indeed tell what's wrong. But it doesn't aid in bug fixing since we do not know in which context it happened. If you instead added information about the item which failed it would help tremendously.

    "An item with the key 'XXXX' has already been added."

    What I'm basically asking is…

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

  6. Implement Automatic Reference Counting (ARC) for .NET

    This would require major work, for sure, but Apple seems to have proven its worth doing.

    For performance sensitive applications, the GC can be a difficult-to-predict performance problem. ARC seems to have solved much of problems with memory management in an elegant way. It would be nice to see this become an *option* in C#/.NET.

    30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  .NET  ·  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. Create a .NET managed wrapper for the Text Services Framework

    Create a .NET managed wrapper for the Text Services Framework

    30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  .NET  ·  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. Create tabbed control like visual studio 2012 has for WPF

    To make a big and complex applications for desktop with a lot of windows please, provide tabbed control for WPF which will have the same functionality as Visual Studio tabbed interface has.

    This will make development of complex applications much more easier and UI will have more functionality.

    30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  .NET  ·  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. Enable alignment of objects on 16/32/... byte boundaries in .NET

    CPU's have had SIMD instructions for many years. Unfortunately, .NET memory allocation methods make it close to impossible to take full advantage of these instructions and reap the significant performance benefits. Even if the JIT compilers don't emit SIMD instructions, many native 3rd party libraries do.

    Objects of a certain size (esp. arrays) should be automatically aligned to take maximal advantage of the CPU platform's SIMD instructions.

    In addition, the .NET Runtime should allow the developer to specify the alignment of objects, especially large arrays but also value types on the stack.

    30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  .NET  ·  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. WCF: Add global namespace for all .NET classes output by svcutil.exe

    The code output by svcutil.exe contains a lot of .NET classes including their namespaces. Here is an example:

    [System.Xml.Serialization.XmlElementAttribute(Form=System.Xml.Schema.XmlSchemaForm.Unqualified, Order=0)]

    If the WSDL you used by chance contains a property named "System", compilation of the generated file fails. I propose to include the global namespace for all references to .NET classes in the output, e.g.:

    [global::System.Xml.Serialization.XmlElementAttribute(Form=global::System.Xml.Schema.XmlSchemaForm.Unqualified, Order=0)]

    This would avoid all possible name clashes. It would work for C# (global::), VB (Global.) and C++ (::). Since the global namespace is a relatively new feature in C# and VB, it should only be added based on the /targetClientVersion command line parameter.

    28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  .NET  ·  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. Framework for bringing WinRT API into "Desktop" world

    What we saw during BUILD is a new world - "Metro style". It's fascinating indeed. But now (a bit later actually but anyway) we have to make one more decision.
    Before when we start designing an app or a system we needed to make single decision - will it "thick" (Windows) and "thin" (Web). It's simplified indeed but in general it is. Now we have to decide: will it be a Metro app (and targets Win8 only), Windows XP-7-8_desktop or Web. It can seem nonsense - why to choose between "Windows" and Metro as they're so different? Metro is touch-based…

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

  12. NetPeerTcpBinding - Please Restore it

    NetPeerTcpBinding has been marked obsolete in Net Framework 4.5.
    There is no substitute for it, and it is valueable in creating small, intercommunication schemes without having to create an elaborate server. This binding seems to work great for simple tasks, why get rid of it? Please do not make this obsolete.

    27 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  .NET  ·  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. Support for wsDualHttpBinding from Portable Class Libraries

    When you create a portable class libraries targeting .NET framework 4.5 and .NET Windows Store from Visual Studio 2012 and you try to add a reference to WCF service with wsDualHttpBinding, Visual Studio is not able to create the service reference and displays the following error: "No endpoints compatible with portable class libraries were found".

    27 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  .NET  ·  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. Add a WebSockets library

    I hereby propose a WebSockets library for the .NET framework, which must be included in all future releases of the .NET from version 4.0 upwards.

    A library providing native support for WebSockets, both server and client applications, must be considered an essential requirement for the next major version of the .NET framework.

    WebSockets provide functionality that is absolutely integral to the future of web applications. The latest version of every major web browser supports WebSockets. Every major browser vendor is adopting the WebSockets API along with the HTML5 specification.

    This type of architecture is already extremely popular and widely used,…

    27 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  .NET  ·  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. Support expressions for ObsoleteAttribute similar to DebuggerDisplayAttribute

    Support expressions for ObsoleteAttribute similar to DebuggerDisplayAttribute so that we could make the warning dynamic to the code that is being marked obsolete. Mainly I would like to use this in combination with the awesome hack that Pablo Fernandez came up with on StackOverflow to produce Custom Compiler Warnings.

    http://stackoverflow.com/questions/154109/custom-compiler-warnings

    Of course just adding a new attribute for producing custom compiler warnings would be great too. Having the warnings able to have a category attached to them would be the icing on the cake.

    26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  .NET  ·  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. KeyNotFoundException

    KeyNotFoundExceptions should include the name of the Key that was not found in the .Data or details. The number of times I have had to attach a debugger and drill deep into the code to figure out that there was a typo in a parameter value is crazy. If I knew what the key was, I could easily say - "oh yeah AccounId, looks like it should be AccountId" or whatever.

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  .NET  ·  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. Support Long file names in System.IO;

    please add support for files longer than 260 char , a solution is already provided by some people that use Win32 API to resolve the issue, but it is time to have this implemented within .NET framework .

    http://gallery.technet.microsoft.com/DelimonWin32IO-Library-V40-7ff6b16c

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  .NET  ·  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. Non-rectangular shapes in Windows RT and Windows Phone

    Please allow us to use non-rectangular polygon shapes with Windows.UI.Xaml.UIElement.Clip in Windows Store apps development. This would help us port the fancy controls (like wpfbookcontrol.codeplex.com) in Windows Store and WP8 worlds.

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  .NET  ·  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. Compress Click Once Deployment Files as you do with XAP

    Update Click Once Deployment to create compressed files (cabs or zip or xap) instead of plain files.
    Simular to what you did for Silverligth (XAP).

    25 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  .NET  ·  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 support for .NET 4.5 on Windows Server 2003 and Windows XP

    Having tracked down a problem on a clients ASP.NET website caused by a bug in .NET 4.0 i wanted to apply 4.5 which contains the fix.

    The infrastructure the website is currently run on is Windows Server 2003. I cannot therefore fix the problem without asking a major government department to spend time and money on providing a new server and without billing a client to migrate their website to a new server.

    This strikes me as foolish move on Microsofts behalf to the point that .NET is now becoming more of a problem than a solution, not only that…

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  .NET  ·  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

Feedback and Knowledge Base