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. provide better design time support for WPF

    I am a devoted user of WinForms' technology, I recently started to develop in WPF 4 and I noticed that my productivity is lowered into creating GUI even banal.
    The Visual Studio designer for WPF can not even remotely stand comparison with WinFroms one, so there are tons of XAML to write by hand.
    In the visual studio designer certainly less functional part is the PropertyGrid that can not be of help if not to set the boolean fields.
    I hope that the next version of VS there is a much better designer

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  2. Make WPF Designer as good as WinForms

    Before adding new features to WPF I'd like to see WPF Designed ("Cider") support to be as good, mature and feature complete as the WinForms designer. For example, creating ToolBars in WPF is practically impossible using the Designer. Also creating simple image buttons requires a lot of manual steps for adding mouse over effects and drawing disabled images.

    14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  3. XAML Debugging

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/351347/xaml-debugging.html
    Serious WPF/Silverlight development really demands that there's the ability to debug XAML, i.e. set breakpoints, step over/into XAML, examine triggers and the likes

    2,939 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  4. Provide native support in the IDE for MVVM

    Something like where VS has a "code mode" for code behind or MVVM or other pattern.

    If MVVM is selected then the IDE helps us fall into the pit of MVVM success.

    Even better would be a coding mode provider model, so other patterns could be plugged in over time

    1,317 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  5. Ensure Xaml compilation through the Roslyn compiler platform

    Currently, there are many requests for Xaml'y features which the community could help introduce if Xaml APIs were available as Roslyn expression trees, etc.

    This would mean the community could create Plugins which could:
    1. Create conditional compilation comments in Xaml
    2. Create or inject hooks to allow for Debugging Xaml
    3. Likely any other idea people can think up.

    Please add support for Xaml to Roslyn, if not already, and provide documentation so we can help introduce our requests as plugins.

    26 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  6. Lock XAML Visual Designer from editing

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/351333/lock-xaml-visual-designer-from-editing.html
    When I am working on a XAML view, I prefer to edit through the text editor, not the visual designer. This causes some grief if I accidentally click and move and element in the designer and mess up all my hand-coded layouts. However, I still want to see the live updates in the visual designer.
    Please add a way for me to lock down the edit capability of the XAML visual designer so that accidental mouse clicks don't mess up hand-coded layouts. Continue…

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  7. WPF Split view - multi screen

    When I write XAML code to create a view I can only split the design window two ways - verticaly or horizontaly.
    But many developers are using more than one screen and I think it would be very nice to be able to split this WPF designer into 2 windows.
    So on one screen developer will see just the design window and on the other screen will be the XAML editor with file related to this design view.

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  8. Fix XDesProc

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/351039/fix-xdesproc.html
    Fix XDesProc.exe so it doesn't hang everyone's systems.

    Just wondering, are you deliberately ignoring this bug, which has been reported by hundreds of developers?

    94 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →

    Rest assured, we’re not deliberately ignoring the bug. Far from it, in fact. The issues with XDesProc are tricky, as I’m sure you’d understand. While the reliability is getting better and we’re seeing a decrease in reported issues, we’re still making some large steps to improve it further. Naturally, if you’ve got any details on what you were doing when XDesProc caused issues, we’d love to hear them and make sure that our efforts address the issues. You can report these issues using the “Report a problem” feature on the Help menu in Visual Studio, and also make sure that you’ve configured Visual Studio to send us crash reports (On the Help menu, select Settings under Send Feedback)

    In the meantime, I can lay your fears to rest and assure you that we’ve redoubled our efforts to make the XAML designer the best designer anywhere.

    -Dante Gagne
    Visual Studio Program…

  9. Allow conditional compile statements in XAML markup

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/351269/allow-conditional-compile-statements-in-xaml-marku.html
    Allow the XAML markup editor to allow conditional compile statements so that a developer could have #ifdef statements in their markup

    433 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  10. Surface [Obsolete] APIs in the XAML designer

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/351266/surface-obsolete-apis-in-the-xaml-designer.html
    When a type (or it's properties) are marked [obsolete] the designer should surface those as designer compile warnings as well.

    80 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  4 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  11. Add ability to debug xaml design mode issues

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/351260/add-ability-to-debug-xaml-design-mode-issues.html
    If you develop an app with blendability in mind (support of designer mode and designer data) it is sometimes very hard to find issues that occur in your code.
    It will be very useful to be able to run debug against "design mode" with breakpoints and so on.

    75 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback!

    This is an idea that we have been actively considering on our team as well. We would love to hear more thoughts from the community around exactly how they would like to see this experience work. For example, should Blend always have a mode where you are running the designer under a Debug mode, or should you be prompted when a particular crash or issue happens, etc.

    Thanks!
    Unni

    Program Manager,
    Visual Studio

  12. Improve the XAML Designer performance

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/351187/improve-the-xaml-designer-performance.html
    It often takes several seconds for a XAML Window to fully display. The editor is constantly pausing as I type, sometimes for as long as a second, before catching up with keystrokes.

    2,011 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    59 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  13. Support XAML refactoring to UserControl / DataTemplate / ResourceDictionary

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/351181/support-xaml-refactoring-to-usercontrol-datatempla.html
    It would be grand if you could highlight a block of XAML and refactor it to a User Control, Control Template or Data Template. Alternatively you could promote all attributes in a selected block into a Style in a ResourceDictionary. Isnt XAML a 1st class citizen? Windows 8 team thinks so.

    33 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  14. Show tooltips in XAML and HTML intellisense

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/351180/show-tooltips-in-xaml-and-html-intellisense.html
    In VB and C# tooltips (form XML comments) are shown for classes, properties and enum values. It's very helpful. Shown them alson in XAML and ASP.NET editors for elements, attributes and enumerated attribute values (also for extensions in XAML).

    43 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  15. XAML refactoring, especially for Rename of properties for Databinding

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/351173/xaml-refactoring-especially-for-rename-of-properti.html
    Currently renaming a property that is databound does NOT rename the binding in the XAML, or the string in the notify property change.

    Ex: Currently, When you change MyInt to be something else

    Backing ViewModel.cs:

    int _myInt;

    public int MyInt // Changes
    {
    get { return _myInt; }
    set
    {
    if (_myInt != value)
    {
    _myInt = value;
    if(PropertyChanged != null)
    {
    PropertyChanged(this, new PropertyChangedEventArgs("MyInt")); /this String does not change
    }
    }
    }
    }

    SomeXaml.xaml:
    <TextBlock Text={Binding MyInt}/> <!-- This MyInt also does…

    193 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  16. Improve WPF Editor performance

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/351170/improve-wpf-editor-performance.html
    Improve Visual Studio WPF Editor performance. With Visual Studio 2010 it is very good, but also a bit slow.

    1,374 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  13 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
1 2 5 6 7 9 Next →

Feedback and Knowledge Base