Would someone comment on issue 9154 please? Performance is important for LoB apps, where we need to display a lot of data items on screen and even WPF was struggling in such scenarios despite virtualization.

At this point the TreeView's ItemTemplateSelector is basiclly broken because the container recycling puts you into a wrong container - there are lots of bugs issued around that.

The Remark section of the SelectTemplateCore method group says you should use SelectTemplateCore(Object, DependencyObject) instead of SelectTemplateCore(Object) for all VirtualizingStackPanels
https://learn.microsoft.com/en-us/windows/windows-app-sdk/api/winrt/microsoft.ui.xaml.controls.datatemplateselector.selecttemplatecore?view=windows-app-sdk-1.5

But this workarounds can only fix ListView and GridView, because by using SelectTemplateCore(Object, DependencyObject), you can no longer set the containers in DataTemplates
(the Selector will assign a standalone container for you), while for the TreeView, you will need a TreeViewItem in the DataTemplate, otherwise you will have no way to bind ItemsSource and IsExpaned property for the child levels of the tree.

Does the WinUI team aware of this issue and if so, any plan to address this? Perhaps, adding a HierarchicalDataTemplate class that allow you to bind data source on the DataTemplate layer like wpf did?

I missed any updates during the BUILD sessions on actual Visual Studio C tooling to bring the developer experience closer to Qt and C Builder, or back to what C /CX used to offer us.

I'd like to know about the coming TableView control if there is something you can share at this point:

• Will it have data virtualization and work with large collections? (for example, > 10,000 items)
• Can we switch the rows and columns and add items horizontally?

For 1.6 and control improvements, is #6945 being looked at? Currently, some (even minor) changes to the default styles require copying and editing the entire XAML style from generic.xaml which is a pain.

As a first step, easy to implement step, it would be nice if all StaticResource bindings within control styles would be replaced with ThemeResource, so at least lightweight styling (overriding the resources) could be used. IMO this is a low hanging fruit, as it is mainly only search and replace 😊

Are there any plans to fix the XAML compiler bug 3331, which breaks winrt::implements in C /WinRT? Thanks for your time and consideration.

WinUI still does not support the x:TypeArguments Directive because it does not support XAML 2009. This makes it impossible to make generic controls such as MyUserControl.
When will WinUI support XAML 2009? MAUI and even WPF do support it.

Stable release for 1.6 planned on Fall 2024, but any estimated date when 1.6 preview will be available to public? Really wanna start playing with native AOT.

Are there any stability fixes in the 1.6 that could improve the multi-select and virtualization issues of the treeview? I couldn't find any hints in the release notes of the latest 1.6 preview. In our application, the treeview issues strongly affect stability. An excerpt of issues can be found in the March WinUI Community Call #9361 (comment)
At that time there was hope that some of these issues get addressed.

Hello,
Can the WinUI team talk about their plans to make WinUI3 officially usable in PowerShell? PowerShell is based on .NET.

There are users on the PowerShell side who want to be able to use WinUI3 but there is no official guidance or even official example of how to do it.

I posted this question on StackOverflow and received some responses: https://stackoverflow.com/questions/78468949/how-to-create-winui3-gui-in-powershell
But none of them are perfect, not all WinUI3 features can be used in PowerShell through those methods. 99% of the time it's because we don't know exactly how to bootstrap WinUI3 in PowerShell, what components and DLLs are exactly required for all WinUI3 functionalities to work in PowerShell.

I'm hoping the WinUI team will go over this topic and provide some guidance, helping material and code examples for how to do this in PowerShell.

P.S I'm totally aware of WPF can be used in PowerShell and I've built GUI based on that and also aware that WPF is being overhauled at the end of this year with Windows 11 themes, however the focus of my post is only about WinUI3 in PowerShell.

When we use Visual Studio, it's extremely easy to setup a C# app that uses WinUI3 with pre-made setups, the same ease of use should be provided for PowerShell users as well or at least there should be a official Microsoft guide that explains how we can do it manually, so we can automate it ourselves through scripts and so on.

Thank you!