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. Unify Single Click Previewing

    Single file preview can be slow. It officially is too slow to turn it on for XAML files.
    It is very confusing having some files opened on single click and some not, without any obvious reason. If it is too slow for the user, he can turn it off.

    Another solution would be to allow to specify which file types should be previewed.
    Related bug report: http://connect.microsoft.com/VisualStudio/feedback/details/705611

    My point is that it is too slow for other types as well, for example aspx files.
    Also it is confusing that some files open on single click and some do not.

    3 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 →

    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. In Windows 10 the new Visual State Managers allow the UI to adapt to different Width and Height. When in debug mode, it will be handy to hav

    In Windows 10 the new Visual State Manager allows the UI to adapt to different Width and Height. When in debug mode, it will be handy to have current window size in overlay (similar to frame rate now)

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    closed  ·  1 comment  ·  UWP / WPF / XAML Tools  ·  Flag idea as inappropriate…  ·  Admin →
  3. Make XAML design view undockedable so that it can be moved to another monitor

    I don't want to get rid of the XAML design view. I just want to make it live on another monitor.

    I also want that single design view to correspond to the XAML text editor view that currently has focus. So when I switch to a different XAML page the design view switches to track it.

    I've seen a few other requests for this (multimon support) that have been marked as completed in VS2015, but as far as I can tell all that has happened is that it is now possible to disable the XAML design view entirely, which is…

    2 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 →
  4. in XAML, give us key commands to format code both into a single line or an attribute per line format

    I know I can turn on 'one attribute per line' formatting option in SETTINGS for XAML editor, but I would like to have two key combinations, one that would reformat an element into 'one attribute per line' format and the other that would reformat that again into a 'all into a single line' format (and that would work more aggresive than current ctrl-F which just indents appropriately the first line, if I am correct).

    namely, I want both options available at the same time, for I often would like to temporary show a XAML element in an attribute-per-line format, and…

    2 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 →

    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 XAML Experiences team is prioritizing other suggestions and closing it at this time. 
     
    If you would like us to reconsider this, please create a new suggestion. Again, thank you for sharing with us! 
     
    Daniel Jacobson
    Program Manager, Visual Studio XAML Experiences Team

  5. Hello : Microsoft Have you presented a competition to develop the phone's screen and who has proposed a keyboard to suit all smartphones For

    Hello : Microsoft
    Have you presented a competition to develop the phone's screen and who has proposed a keyboard to suit all smartphones Format
    Now I want to show you the keyboard and how they work and wages marketed either program with the device or in the Apps store .
    I hope you like it .

    Suhil Saghier

    2 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 →
  6. Notify developer that "Create data binding..." will remove custom binding expression.

    I often use a subclass of the Binding markup extension. It would be nice if the XAML tool could warn me that I am losing that when I select "Create data binding...." I can't tell you how many times my validation stops working because the XAML editor replaced custom Binding extension with the vanilla version.

    2 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 →

    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 XAML Experiences team is prioritizing other suggestions and closing it at this time. 
     
    If you would like us to reconsider this, please create a new suggestion. Again, thank you for sharing with us! 
     
    Daniel Jacobson
    Program Manager, Visual Studio XAML Experiences Team

  7. Indent nested properties correct for format document/section

    Then format document/section.
    The indent for elements works fine, but properties that are on "next line" don't follow correct.
    And good xaml code-style is to have the properties o separate lines under the element.

    2 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 →

    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. 2 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 →
  9. Make WPF XAML designer work with custom Window controls.

    We need the VS designer to work with custom Window controls, and custom window styling.

    2 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 →
  10. Preview of colors and brushes in static/dynamic resource bindings

    In large WPF projects there are sometimes many colors and brushes. To help the developer to get the correct binding to the ressource it is helpfull to show the color in xaml.
    The tool "Inline Color Picker" from https://visualstudiogallery.msdn.microsoft.com/86afb3bf-e14e-4a35-817e-4580a95cf33c
    is a great help, but thos works only on direct colors/brushes.
    The idea is to use this tool (integrated in Visual Studio) and add support for static/dynamic resource extensions.

    2 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 →

    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 XAML Experiences team is prioritizing other suggestions and closing it at this time. 
     
    If you would like us to reconsider this, please create a new suggestion. Again, thank you for sharing with us! 
     
    Daniel Jacobson
    Program Manager, Visual Studio XAML Experiences Team

  11. Control.FontFamily smarter IntelliSense

    In a XAML file.

    <Label Grid.Column="1" VerticalAlignment="Center" FontFamily=""

    FontFamily values should appear automatically.

    In this case I was typing the samples and I needed Trebuchet MS like this.

    <Label Grid.Column="1" VerticalAlignment="Center" FontFamily="Trebuchet MS"

    I checked Control.FontFamily Property at MSDN but I could not find all the possible values there either.

    I also suggest an update to that prperty with all the possible values at MSDN.

    1 vote
    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 →
  12. Keyboard navigation form Code to XAML

    Navigating from C#-code to XAML-code by typing Strg-Tab keys activates the Preview of the Designer. When then typing i.e. cursor-up I move the selected element. This way I often do things I didn´t want to do, because I wnated to edit the code and not move any control. I think that is not what most coders want. I think most prgrammes want the cursor to be set into the XAML-code window. To activate the XAML code window I have to press shift-F7 (after after Strg-Tab).
    For me it would be fine to have any possibility to deactivete the editing in…

    1 vote
    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 →
  13. ImageBrush ImageSource smarter IntelliSense

    In a XAML file.

    <Grid>
    <Grid.Background>
    <ImageBrush ImageSource=""

    ImageSource should automatically display all the image files already in the project.

    In this case I only had one which was watermark.png

    Therefore the code should automatically look like this:

    <ImageBrush ImageSource="watermark.png"

    If there are ZERO IMAGES files in the project then Visual Studio should be smart enough to request a new image for the project.

    1 vote
    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 →

    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. Use Blend (Photoshop) Hotkeys in XAML designer

    To make XAML editing more like Blend, include the photoshop hotkeys (ie: "H" for hand panning, and "V" for selecting, etc..). This made designing and fine-tuning the interface more productive in Blend, especially if you're used to Photoshop.

    1 vote
    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 →

    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. Fix XAML multi-line auto complete issue

    Intellisense will only complete one line when writing with multiiple lines selected in the XAML editor.

    1 vote
    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 →

    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 XAML Experiences team is prioritizing other suggestions and closing it at this time. 
     
    If you would like us to reconsider this, please create a new suggestion. Again, thank you for sharing with us! 
     
    Daniel Jacobson
    Program Manager, Visual Studio XAML Experiences Team

  16. The Visual Studio won't start after applying Update 2

    I don't post this vis SendFeedback because the VS won't start.
    Below is the exception:
    Application: devenv.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an unhandled exception.
    Exception Info: System.InvalidCastException
    at Microsoft.VisualStudio.PlatformUI.BranchRepositorySwitcher.System.Windows.Markup.IComponentConnector.Connect(Int32, System.Object)
    at MS.Internal.Xaml.Runtime.ClrObjectRuntime.SetConnectionId(System.Object, Int32, System.Object)

    Exception Info: System.Windows.Markup.XamlParseException
    at System.Windows.FrameworkTemplate.LoadTemplateXaml(System.Xaml.XamlReader, System.Xaml.XamlObjectWriter)
    at System.Windows.FrameworkTemplate.LoadTemplateXaml(System.Xaml.XamlObjectWriter)
    at System.Windows.FrameworkTemplate.LoadOptimizedTemplateContent(System.Windows.DependencyObject, System.Windows.Markup.IComponentConnector, System.Windows.Markup.IStyleConnector, System.Collections.Generic.List`1<System.Windows.DependencyObject>, System.Windows.UncommonField`1<System.Collections.Hashtable>)
    at System.Windows.FrameworkTemplate.LoadContent(System.Windows.DependencyObject, System.Collections.Generic.List`1<System.Windows.DependencyObject>)
    at System.Windows.StyleHelper.ApplyTemplateContent(System.Windows.UncommonField`1<System.Collections.Specialized.HybridDictionary[]>, System.Windows.DependencyObject, System.Windows.FrameworkElementFactory, Int32, System.Collections.Specialized.HybridDictionary, System.Windows.FrameworkTemplate)
    at System.Windows.FrameworkTemplate.ApplyTemplateContent(System.Windows.UncommonField`1<System.Collections.Specialized.HybridDictionary[]>, System.Windows.FrameworkElement)
    at System.Windows.FrameworkElement.ApplyTemplate()
    at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)
    at System.Windows.UIElement.Measure(System.Windows.Size)
    at Microsoft.Internal.VisualStudio.PlatformUI.WorkerThreadElementContainer.InnerMeasure(System.Windows.Size)
    at Microsoft.Internal.VisualStudio.PlatformUI.WorkerThreadElementContainer+<>c__DisplayClass14_0.<MeasureOverride>b__0()
    at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
    at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
    at System.Windows.Threading.DispatcherOperation.InvokeImpl()
    at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
    at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
    at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object,…

    1 vote
    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 →

    Thanks for your feedback. We completely understand that since VS is not starting, you would not be able to report a problem that way. However, please do note that for each crash, we do get enough telemetry to understand the problem via Windows Error Reporting. Also, you could consider filing an issue at http://connect.microsoft.com (UserVoice is not the appropriate forum for reporting crashes).

    Thanks,
    Unni
    Program Manager, Visual Studio

  17. It would be nice if there were a setting that made going directly to the xml editor the default for xsd files rather than the designer.

    I am blind and find working with schema files in the editor far easier than trying to use the designer. As it is now if I default open an xsd file I get the designer and the only thing I ever do with it is trigger the view in editor control.

    1 vote
    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 →

    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. It would be great to have the option to set a DesignTime background color. Something like d:DesignTimeBackground="White"

    It would be great to have the option to set a DesignTime background color. Something like d:DesignTimeBackground="White"

    Normally user controls design is done with transparent background, but details can get lost or missed. It can be helpful to be able to set a background at design time, especially if the controls are complex, as it makes things stand out better - for example, if you have 1px lines that will be black or a dark color, you wouln't see them clearly on the designer's normal surface transparent color, which is also dark.

    It would also be preferable to do design…

    1 vote
    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 →

    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 XAML Experiences team is prioritizing other suggestions and closing it at this time. 
     
    If you would like us to reconsider this, please create a new suggestion. Again, thank you for sharing with us! 
     
    Daniel Jacobson
    Program Manager, Visual Studio XAML Experiences Team

  19. Allow Setting ScrollViewer Position in XAML

    When using the ScrollViewer, we often want to see what our UI will look like when the content is scrolled to different positions, yet the scroll position of the ScrollViewer cannot be set in XAML, therefore making this not possible. Also, we are unable to use Storyboards and Animations to scroll the ScrollViewer. I think being able to set the scroll position of the ScrollViewer in XAML would make design much easier.

    1 vote
    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 →

    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 XAML Experiences team is prioritizing other suggestions and closing it at this time. 
     
    If you would like us to reconsider this, please create a new suggestion. Again, thank you for sharing with us! 
     
    Daniel Jacobson
    Program Manager, Visual Studio XAML Experiences Team

  20. In XAML why don't use ".Member" replace "Father.Member" ?

    Like this:
    <ResourceDictionary>
    <ResourceDictionary.MergedDictionaries>
    why don't use <.MergedDictionaries> replace <ResourceDictionary.MergedDictionaries>?

    1 vote
    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 →

    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 XAML Experiences team is prioritizing other suggestions and closing it at this time. 
     
    If you would like us to reconsider this, please create a new suggestion. Again, thank you for sharing with us! 
     
    Daniel Jacobson
    Program Manager, Visual Studio XAML Experiences Team

Feedback and Knowledge Base