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. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    18 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    59 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  13 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  6. Only display real errors on "Error List" after compilation (option?)

    If you open a large XAML project, it's not uncommon to have a lot of false errors displayed in "Error List" tab, (mainly about XAML files)

    Is it possible to add a button to clear completely this list and display only real errors detected by the compiler (just a simple parsing of the compiler output) ?

    It would help a lot of developers cause the only solution right now is to copy-paste the output in Notepad and search "error"...

    See the attachment

    406 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  7. Visual studio 2017: Add support for Windows store 8 projects (Phone & Desktop).

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/351484/visual-studio-2017-add-support-for-windows-store-8.html
    add projects support for Windows Store 8.1 and 8.0, and Windows Phone 8.1 and 8.0 in VS 2017 RTM

    293 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    17 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  9. Fix the UWP designer errors

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/351513/fix-the-uwp-designer-errors.html
    I've been doing XAML for 9 years, but the current status of XAML designer in UWP apps is just terrible. Either remove it completely or make it at least as stable as WPF designer in VS2015.

    Things like:

    Method not found: Void Windows.UI.Composition.Visual.put_Size(System.Numerics.Vector2)

    or COMException: Error HRESULT E_FAIL has been returned from a call to a COM component.

    I haven't met a single UWP developer who wasn't frustrated by the designer always broken

    112 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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…)
    Password icon
    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…

  11. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  4 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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…)
    Password icon
    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

  13. XAML designer for Xamarin Forms

    Are there any plans to support Xamarin Forms in the XAML designer? We currently have the previewer window, but it’s only one way, and it would be fantastic to have first class drag and drop visual design experience.
    For the love of God, because they have not yet implemented a Designer compatible with Xamarin.Forms is something extremely and widely requested a long time and so far not even a pre Alpha version, it is very sad and disheartening to see Microsoft ignoring the developers.

    47 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  15. Allow VisualStudioToolsManifest.xml to be TFM specific

    In NuGet packages we can now place a file in \tools\VisualStudioToolsManifest.xml that list the set of controls that should be added to the Toolbox in the visual studio XAML designer. This works both for UWP and WPF.
    However there's no way to make this TFM specific. This poses a problem if you for instance have both WPF and UWP controls in your nuget package and the set of controls is not 100% the same, or if you are providing multiple TFV where for instance newer TFV provides extra controls and deprecates older ones. Ie UAP10.0.14393, UAP10.0.16299, or net451, net461 etc. …

    40 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  16. Collapse to definitions on XAML with CTRL+M+O like happen on C# code.

    This suggestion is migrated to Developer Community. Please use below link to view the current status.
    https://developercommunity.visualstudio.com/content/idea/351382/collapse-to-definitions-on-xaml-with-ctrlmo-like-h.html
    To collapse nodes in XAML we have to do CTRL+M+M or use the mouse to collapsed eash node.
    Will be nice to have a shortcut like in the C# editor that collapse all the nodes.

    37 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  17. Innovate the Xaml Designer, Dawg

    This is in regards to the following link and comment:
    https://blogs.msdn.microsoft.com/visualstudio/2017/09/11/a-significant-update-to-the-xaml-designer/#comment-285146

    The high level goal here is to reduce the amount of time and therefore cost in developing highly functional and reliable applications. The primary value in Xaml is that, unlike code and imperative instructions, it is easily parsed by a designer and tooling. Additionally, it lowers the barrier to entry so that a greater number of resources within an organization can utilize and work with it during the lifetime of an application.

    The ask here is simple: please start thinking of Xaml as an *application*-definition language, rather than one…

    34 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  18. wpf svg

    Please enable wpf image box to load svg graphic file. It's ridiculous for a XAML based UI to be able to load common bitmap images (BMP, JPG, PNG) but not SVG.

    34 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 8 9

Feedback and Knowledge Base