Because Microsoft will not develop DirectX for Windows 7, its latest desktop OS version since Windows 8.x and 10 are a mobile and limited OS (also ugly), they are not desktop operating systems, Microsoft should support Vulkan in WPF that runs on any version of Windows, including Windows 7 which has the largest market share and installed base, without the need or obligation to update an operating system that nobody wants.

In Microsoft "Mobile first, cloud first" era, that really means "Mobile only, cloud only", is frustrating how Microsoft completely abandon the desktop, including OS's, applications and developing support for desktop. Nobody wants to migrate to the limited UWP mobile model.

I use the Grid for most of the XAML I write. Right now it becomes difficult to move controls within a Grid around:

<Grid>
<Grid.RowDefinitions>
<RowDefinition Height="Auto" >
<TextBlock Grid.Column="0" Text="ABD" />
<TextBox Grid.Column="1" Text="ABD" />
</RowDefinition>
<RowDefinition Height="*" />
</Grid.RowDefinitions>
<Grid.ColumnDefinitions>
<ColumnDefinition Width="*" />
<ColumnDefinition Width="Auto" />
</Grid.ColumnDefinitions>
<Grid>

Thus anything within a ColumnDefinition or RowDefinition Content would automatically be included in that definition.

SplitViewPanePlacement has a Left and Right option

Would like to request a Top and Bottom option as well for greater versatility.

Please implement the x:Bind feature from Universal Windows Apps in WPF.

See http://channel9.msdn.com/events/Build/2015/3-635 for a presentation on x:Bind.

It would be great of the Document Outline pane would show the contents of ResourceDictionaries

Please fix the System.Windows.Controls.Ribbon ( https://msdn.microsoft.com/en-us/library/system.windows.controls.ribbon.ribbon(v=vs.110).aspx )

It has several issues:
- no Office 2013 style
- window is too small
- ...

https://connect.microsoft.com/VisualStudio/feedback/details/775972/wpf-ribbon-window-the-border-is-too-thin

"Gepost door Sachin [MSFT] op 27/02/2015 om 12:26

The WPF team has reviewed this issue and is unable to address it at this time as we are working on higher priority issues for the WPF community. We thank you for the feedback and may consider this issue again while triaging issues for a future version of WPF. – WPF team"

Please have a look at it again instead of closing the ms connect ticket.

EdgeHTML is available for UWP (Universal Windows Platform). Please, add support also for WPF. The old WebBrowser control with Internet Explorer interop has too many limitations and drawbacks in these days.

Thank you

In addition, very welcome feature:
Scrollbar templating

allow for binding all available events (click, leftmosuebuttondown, ...) right in visual studio.

In WPF e.g. for a TextBox databindings are usually using UpdateSourceTrigger="LostFocus".

This is however broken in various ways. For example put the textbox in a TabControl, edit the text and switch tab. The data is lost.

There are various "workarounds" but they all have their own problems. This is a well known bug and it should be fixed.

(Or at least an alternative UpdateSourceTrigger="LostFocusFixed" mode should be added that actually works all the time.)

Hi!

I'm using DrawingVisual very much to render different objects to the screen. The function .PushEffect is right now obsolete and does not work. It would be really neat to get an updated version that has the hardware capabilities. It would also be really nice to be able to push custom HLSL shaders too. Because i want to use multiple effects on the same DrawingVisual, this is not possible right now since you only can have one effect through the DrawingVisual.Effects property.

Thanks guys! :)

WebAssembly or wasm is an experimental efficient low-level programming language for in-browser client-side scripting, which is currently in development. WebAssembly is portable bytecode which is designed to be faster to parse than JavaScript, as well as to execute faster. The team working on WebAssembly include people from Mozilla, Google, Microsoft, and Apple (who respectively control the four major browsers, Firefox, Chrome, Internet Explorer, and Safari).

https://github.com/WebAssembly/design/blob/master/FAQ.md

many control has a header, is a good idea. but the header can only placed on the top of control. I think the header should can be placed on the left option;

Please follow the footsteps of the ASP .NET team and make WPF open-source with the source code on GitHub, and accept pull-requests from the community.

Reverse the decision to render all content as bitmaps across RDP, as described here: https://blogs.msdn.microsoft.com/jgoldb/2008/05/15/whats-new-for-performance-in-wpf-in-net-3-5-sp1/

Allow for something similar to NgIf, NgFor, NgSwitch... right in xaml for the development of wpf applications. That is, allow for the basic If, For and Switch statements right inside xaml.

It's probably the hardest task in WPF to have a selectable piece of text. While TextBox can be restyled to look like a TextBlock, it certainly doesn't have it's features like Runs, Hyperlinks, etc.

<TextBlock Selectable="True">
<Run Text="{Binding SomeText}" />
<LineBreak />
<HyperLink ...>OtherText</HyperLink>
</TextBlock>

that allows to select the text and being able to copy it's plaintext would already be enough for almost any case.

When creating a new WPF application using Visual Studio 2015 the main window that is created defaults to a size that is not convenient for some projects. Instead of having to alter XAML code or physically alter the main window dimensions for every new window created why not provide a default configuration setting for the main window size so that every new item that is added to a project has the same default main window size?