Suggested plan for the next version 1.8

[ghost1372]

These are things we need and have been asking for years but have never been considered.

I hope Microsoft will consider this list. Also, if nothing is going to happen to any of the items, we expect a proper explanation so that we don't have to waste our time waiting to deal with it.

Instead of working on trivial things, focus on the following:

Controls

Name	Remark
Splitter	microsoft/microsoft-ui-xaml#5346
Inking Controls
DataGrid/TableView
PagerControl	Available in all Experimental Releases but never released to Stable/Preview microsoft/microsoft-ui-xaml#60

Features/APIs

Name	Remark
Kiosk Mode	#3642
Windowing improvements	Xaml Properties (Binding Support, Width, Height, Min/Max,...) microsoft/microsoft-ui-xaml#10358, Move AppWindow Stuffs to Window Class
AllowsTransparency	microsoft/microsoft-ui-xaml#10311 (comment)
Input Validation	microsoft/microsoft-ui-xaml#179
WinUI 3 XAML Designer	microsoft/microsoft-ui-xaml#5917
Smooth App Resize	microsoft/microsoft-ui-xaml#5148 (comment)
ApplicationData.GetForUnpackaged	No ETA
AOT Support for Custom Control	microsoft/microsoft-ui-xaml#10409 microsoft/microsoft-ui-xaml#10214
Custom Control Improvements	Using xBind, Commands, AnccesstorType in ResourceDictionary, Improving TemplateBinding for using with Converters, microsoft/microsoft-ui-xaml#7003
ResourceDictionary Improvements	Using xBind
Binding/xBind Improvements	microsoft/microsoft-ui-xaml#2508 microsoft/microsoft-ui-xaml#560
Pin To Taskbar for UnPackaged Apps	#3917
Non-XAML ThemeResource	microsoft/microsoft-ui-xaml#10029
Drag and Drop support for Elevated Apps	microsoft/microsoft-ui-xaml#7690
Add alternate label placement to ToggleSwitch	microsoft/microsoft-ui-xaml#3696
Improved StorageFile APIs	#8
Xaml Improvements	microsoft/microsoft-ui-xaml#6569 microsoft/microsoft-ui-xaml#7037 microsoft/microsoft-ui-xaml#279 microsoft/microsoft-ui-xaml#929
Xaml2018	#5250 (comment)
Unseal all the things	microsoft/microsoft-ui-xaml#780
Windows 10/11 Shell Context Menu	#1082
Improve Cursor API (Change Mouse Cursor and More...)	#1816 microsoft/microsoft-ui-xaml#506
Enable ItemsView selection via binding	microsoft/microsoft-ui-xaml#10504
Enable Application.RequestedTheme at Runtime	microsoft/microsoft-ui-xaml#4474 microsoft/microsoft-ui-xaml#2991
Splash screen	microsoft/microsoft-ui-xaml#4055
Set x:Uid from Code-Behind	microsoft/microsoft-ui-xaml#10575
SVG compatibility	microsoft/microsoft-ui-xaml#1494

Bug Fix

Name	Remark
Address top quality and experience issues
Slow Windows and Flickering	microsoft/microsoft-ui-xaml#10259
Numberbox Rounding Issue
Application.RequestedTheme
Hyperlink Button not working with Uri like mailto:email	microsoft/microsoft-ui-xaml#4438 microsoft/microsoft-ui-xaml#5630 microsoft/microsoft-ui-xaml#10448 microsoft/microsoft-ui-xaml#10428
Creating Window in App ctor	microsoft/microsoft-ui-xaml#8664
Binding to bool shows Windows.Foundation.IReference`1	microsoft/microsoft-ui-xaml#4266
x:Bind does not work with C# record	microsoft/microsoft-ui-xaml#5315

TitleBar Bug Fix

Name	Remark
Title bar is stuck and not working	https://github.com/microsoft/WindowsAppSDK/issues/5490
TitleBar title doesn't propagate to window	microsoft/microsoft-ui-xaml#10557
Incorrect spacing when using a short title	microsoft/microsoft-ui-xaml#10492
Resizing from top window border does not resize the contents with the new TitleBar control	microsoft/microsoft-ui-xaml#10454
TitleBar control content misalignment and cropping after maximizing and dragging	microsoft/microsoft-ui-xaml#10427
CenterContent in TitleBar control does not stretch properly	microsoft/microsoft-ui-xaml#10421
TitleBar has too much whitespace in collapsed mode	microsoft/microsoft-ui-xaml#10410
WinUI TitleBar - Resize behavior broken if TitleBar.IconSource is set	microsoft/microsoft-ui-xaml#10374
Setting the maximize region of a win32 window using InputNonClientPointerSource secretly reverts back to default	microsoft/microsoft-ui-xaml#10379
Setting the titlebar control back button visible through C# for the first time allows it to be dragged and removes animation	microsoft/microsoft-ui-xaml#10350
TitleBar control calculation of padding is incorrect	microsoft/microsoft-ui-xaml#10344
New TitleBar control with PathIconSource as IconSource breaks the app	microsoft/microsoft-ui-xaml#9784
Double-click on XAML TitleBar icon doesn't close the window	microsoft/microsoft-ui-xaml#9907
TitleBar doesn't respect AppWindow.TitleBar.IconShowOptions	microsoft/microsoft-ui-xaml#9864
Cannot set color of Title and Subtitle text in TitleBar	microsoft/microsoft-ui-xaml#9866
Cannot set the Background color of a TitleBar	microsoft/microsoft-ui-xaml#9865
TitleBar doesn't respect AppWindow.TitleBar.PreferredHeightOption	microsoft/microsoft-ui-xaml#9863

Tip

Completed features or fixes that have been implemented successfully.

Done

Name	Remark
Picker	Available in v1.8-exp1, Probably coming in v1.8, PR Merged
Appx/MsixBundle	Probably coming in v1.8, Nuget Package Exist
App Freeze and Stop rendering in remote desktop	Done 1 2 3

[MartinRobins]

As I have said elsewhere, Windows App SDK is no good for business applications until such time as there is a working UI validation framework. Personally, I am happy with the interfaces available in WPF (though many on here disagree with me and feel something better could/should be provided) - especially as it would make for easier reuse of existing back-end code - but at least give us something.

[ghost1372]

Yes, I sometimes use WPF, but I hope WinUI can achieve what it deserves.

[MPITech]

And I have said elsewhere, but I will repeat here, not being able to bind numberboxes to decimal (currency) values is about just as bad for business applications as not having validation. Anyone who works with currency values knows to use decimal to store them in SQL Server or other DB and in C#. When you bind numberboxes to decimal indirectly using a double-to-decimal and vice-versa conversion, you run the risk of rounding issues, making it near impossible for us to continue with our business application appropriately. I don't know what to do but BEG someone to fix this. WinUI is great, but this and some of the other issues above really are preventing mass adoption and it is such a shame.
Thanks for reading.

[DrusTheAxe]

the WinUI NumberBox's "Value" property is unfortunately tied to double currrently

This has been a fun area of internal discussion of late, as you'd no doubt imagine. I've heard a few ideas floated from 'teach NumberBox how to also work with decimal' to 'make a new DecimalBox', with the latter sounding like the odds on favorite from the mutterings I've heard of the WinUI experts. We shall see.

I don't know concrete details other than there's a lot of interest here. As you know we just had the Build conference so a lot of people were busy either directly or indirectly supporting the efforts, so please be patient as folks unwind from very full schedules making Build happen and rock back into the more usual work cadence. @RDMacLachlan is keenly aware of the interest and working to help focus efforts to deliver. I'm sure you'll hear more as soon as we have news to share.

[dotMorten]

@DrusTheAxe We had an interesting discussion on this at Build, and I quickly hacked something up that might work. It can be done with attached dependency properties. So you could have something like this:
<NumberBox NumberBox.DecimalValue="{Binding MyDecimal, Mode=TwoWay}" />
The Value property would still return a double-version of MyDecimal, but MyDecimal will be updated internally with the right increments, to keep the precision going.
It does add the complexity of also needing equivalent attached properties for min/maxvalue and increment values, but the nice thing is we'd now also be able to add Integer and other types, without binding-issues, and not break NumberBox or add duplicate implementations of NumberBox.

[whiskhub]

Thanks for keeping the community updated @DrusTheAxe!

[MPITech]

@DrusTheAxe Thank you so much for the update!
@dotMorten That sounds like a great approach. Thanks for your efforts!

I am so happy to hear about the progress on this.

[DrusTheAxe]

@DrusTheAxe We had an interesting discussion on this at Build, and I quickly hacked something up that might work. It can be done with attached dependency properties. So you could have something like this: <NumberBox NumberBox.DecimalValue="{Binding MyDecimal, Mode=TwoWay}" /> The Value property would still return a double-version of MyDecimal, but MyDecimal will be updated internally with the right increments, to keep the precision going. It does add the complexity of also needing equivalent attached properties for min/maxvalue and increment values, but the nice thing is we'd now also be able to add Integer and other types, without binding-issues, and not break NumberBox or add duplicate implementations of NumberBox.

Interesting. @RDMacLachlan and I'll pass along word to the folks working on the WinUI support for consideration (if not already considered :-) )

[myokeeh]

I love that you listed Kiosk Mode. I appreciate it.

[shelllet]

missing drag& drop support elevated ,@https://github.com/microsoft/microsoft-ui-xaml/issues/7690

[zipgenius]

..…and a better drag&drop handling, too.

[ghost1372]

done

[dongle-the-gadget]

Unfortunately, I believe this is a lost cause (Windows limitation). It already doesn't work for packaged Win32 apps, let alone Windows App SDK ones.

[mominshaikhdevs]

Unfortunately, I believe this is a lost cause (Windows limitation). It already doesn't work for packaged Win32 apps

the underlying Win32 API do support this functionality since the Vista days. It's the MSIX tech that is pure shit. So, this is a MSIX Bug/Limitation that will need to be fixed in the newer Windows versions. Just like this one: #2555 (#2555 (comment)). (that also, assuming MS is serious about MSIX, if at all).

[shelllet]

Unfortunately, I believe this is a lost cause (Windows limitation). It already doesn't work for packaged Win32 apps

the underlying Win32 API do support this functionality since the Vista days. It's the MSIX tech that is pure shit. So, this is a MSIX Bug/Limitation that will need to be fixed in the newer Windows versions. Just like this one: #2555 (#2555 (comment)). (that also, assuming MS is serious about MSIX, if at all).

I believe the problem lies in the direction and the decisions made. Computers are tools to assist people in their work. To sacrifice convenient functions for the sake of security is extremism.

[HotCakeX]

Please include fixing this issue in v1.8 too. It prevents the WinUI3 apps from being used in Hyper-V VMs and some other remote desktop scenarios because it causes a lot UI freezing.

microsoft/microsoft-ui-xaml#10009

[ghost1372]

done

[HotCakeX]

Ty 🙏

[bogdan-patraucean]

@ghost1372 it's not just related to VMs, here is another issue where I linked similar ones already reported.

[bogdan-patraucean]

it might also be related to this one, which should arrive in 1.7, according to @codendone

[ghost1372]

@bogdan-patraucean i added your issues to list

[danielgruethling]

I hope they look at numberboxes in general. There's so many problems with them.

• Here's broken bindings: ListView of NumberBox with Minimum constraint corrupts value when ordered microsoft-ui-xaml#10182
• Child controls missing on the visual tree when the numberbox is invisible at application start: NumberBox do not have their child controls on the visual tree when the NumberBox is initially invisible microsoft-ui-xaml#8752
• Also missing features a lot of people asked for years ago: Proposal: NumberBox V2 - Polish API with Additional Properties and Events microsoft-ui-xaml#3158
• Broken input NumberBox will sometimes not respond to input from the keyboard microsoft-ui-xaml#10286
• Breaking other input Changing the NumberBox value with Arrow Keys makes the UI unresponsible for the mouse. microsoft-ui-xaml#10223
• Broken rounding NumberBox displays double 3.12 as 3.1999999999..... microsoft-ui-xaml#9826

I could list more issues with numberboxes but just searching this repo will list a lot more.

[MPITech]

Wow, NumberBox is even worse than I realized so far. I got stuck in our app with it not supporting decimal, I didn't even notice half of these problems yet. What a mess.

[tpoint75]

And NumberBox displays 1e15 as 1000000000000000 only.

[DrusTheAxe]

See [Experimental] Decimal data type #5375 :-)

[sylveon]

Pin to taskbar is very unlikely to happen. Microsoft has pretty vocally stated that they do not want such an interface: https://devblogs.microsoft.com/oldnewthing/20141230-00/?p=43273

[ghost1372]

Pinning is currently possible for packaged apps. While Microsoft has restricted it to unpackaged applications, there is a way to get around it.
https://github.com/castorix/WinUI3_PinToTaskbar/blob/master/Pin/Pin/dllmain.cpp

It is now possible to pin any app with c# and unpackaged mode. But why not create a standard way? Must definitely be revised in decisions

[sylveon]

Read the article.

[Balkoth]

Isn't this exactly done like theoldnewthing describes by driving the context menu? Just because something can be done does not mean it should be done.

[Gaoyifei1011]

These are things we need and have been asking for years but have never been considered.

I hope Microsoft will consider this list. Also, if nothing is going to happen, we expect a proper explanation. Also, if nothing is going to happen to any of the items, we expect a proper explanation so that we don't have to waste our time waiting to deal with it.

Instead of working on trivial things, focus on the following:

Controls

Name Remark
Splitter microsoft/microsoft-ui-xaml#5346
Inking Controls
DataGrid/TableView
PagerControl Available in all Experimental Releases but never released to Stable/Preview

Features/APIs

Name Remark
Kiosk Mode #3642
Windowing improvements Xaml Properties (Binding Support, Width, Height, Min/Max,...)
AllowsTransparency microsoft/microsoft-ui-xaml#10311 (comment)
Input Validation
Designer
Smooth App Resize
ApplicationData.GetForUnpackaged
AOT Support for Custom Control microsoft/microsoft-ui-xaml#10409 microsoft/microsoft-ui-xaml#10214
Custom Control Improvements Using xBind, Commands, AnccesstorType in ResourceDictionary, Improving TemplateBinding for using with Converters, microsoft/microsoft-ui-xaml#7003
Binding/xBind Improvements
Picker Currently Draft/Experimental API
Pin To Taskbar for UnPackaged Apps #3917
Non-XAML ThemeResource microsoft/microsoft-ui-xaml#10029
Drag and Drop support for Elevated Apps microsoft/microsoft-ui-xaml#7690
Add alternate label placement to ToggleSwitch microsoft/microsoft-ui-xaml#3696
Improved StorageFile APIs #8
Xaml Improvements microsoft/microsoft-ui-xaml#6569

Bug Fix

Name Remark
Address top quality and experience issues
Slow Windows and Flickering microsoft/microsoft-ui-xaml#10259
Numberbox Rounding Issue
Application.RequestedTheme
App Freeze and Stop rendering in remote desktop microsoft/microsoft-ui-xaml#10009 microsoft/microsoft-ui-xaml#10213 microsoft/microsoft-ui-xaml#10091
Hyperlink Button not working with Uri like mailto:email microsoft/microsoft-ui-xaml#4438 microsoft/microsoft-ui-xaml#5630

Feature should also include xaml 2009 in .net

[ghost1372]

tnx, i added microsoft/microsoft-ui-xaml#7037 to list

[HMO-SOUL]

Before requesting anything, i want to thanks the WASDK team for their hard work and effort, i understand it's hard for you to manage the project with few team members and i dearly hope MS will give you more funds and human resources

I want to request making the Window control inherit from DependencyObject this will make extending and fixing bugs much easier, like creating a BaseWindow class the inherit from DependencyObject and combines it with the current window control functionalities then making the window control inherit from BaseWindow might leads to more benefits and improvements

Thanks for reading my post, i appreciate WinUI 3 and WASDK and their team

[weitzhandler]

This post is so refreshing to see 💝

Thanks for the WinUI team for the continued efforts. WinUI has been continuously neglected by MS and I'm glad to see it's being worked on.
To me the most important factor is to first make sure the XAML functionality and capabilities we're used to from WPF should at least be met. That includes microsoft/microsoft-ui-xaml#10473, general ElementName and AncestorType support in x:Bind or any adequate alternative (why shouldn't it be able to work as a compiled binding?), but definitely other more general things like validation etc.
There are muliple issues with TreeViewItem.IsExpanded and TreeViewNode.IsExpanded not working properly.

[weitzhandler]

@RDMacLachlan @codendone is anyone in the team actually reading these posts (or this one)?

[RDMacLachlan]

Hi everyone,
Very much so! We greatly appreciate the input from everyone and all the work @ghost1372 has done to assemble the requests. We're working with the various WinAppSDK component teams to create a plan.

[MPITech]

Hi everyone, Very much so! We greatly appreciate the input from everyone and all the work @ghost1372 has done to assemble the requests. We're working with the various WinAppSDK component teams to create a plan.

@RDMacLachlan has just restored my faith in humanity.

[ghost1372]

Hi @RDMacLachlan
We are happy to see that our voices have been heard. I hope everything goes well.
Fans have been treated unfairly for years. I hope good things happen, and if something doesn't go well, at least we deserve some explanation.
Thank you

[Balkoth]

This thread and the 1.7 release thread show that there are still people that want to move the platform forward. Please don't continue as the previous releases where the community around WinAppSDK was mostly ignored.

[Gaoyifei1011]

[ghost1372]

Yes, fortunately it has been merged.

[Gaoyifei1011]

[HMO-SOUL]

A C#/WinRT rewrite? Can you give me a link talking about that? I'm interested

[Gaoyifei1011]

A C#/WinRT rewrite? Can you give me a link talking about that? I'm interested

https://github.com/microsoft/CsWinRT/tree/fhl/cswinrt-3.0/src/WinRT.Runtime2

[HMO-SOUL]

Thanks

[ghost1372]

I think if xbind is implemented for the ResourceDictionary (No Code-Behind), most of the AoT problems for custom controls will be solved.
Have they planned anything useful for custom control in v3.0?

[Gaoyifei1011]

[mominshaikhdevs]

Drag and Drop support for Elevated Apps，This is actually a problem of Windows rather than a problem of the WinUI3 framework. This issue exists in all the Win32 desktop applications.

The issue stems from the privilege isolation of the user interface. You can click this link to learn more about it.

This Issue can be easily solved by introducing a "IL Broker Manager (Service)" in Windows, if MS really wanted to fix it.

[Gaoyifei1011]

[ghost1372]

Thank you, I added it.

[MPITech]

@Gaoyifei1011 You reposted the long, original post eight times in your responses. Please try to not do that 😉

[Gaoyifei1011]

@Gaoyifei1011 You reposted the long, original post eight times in your responses. Please try to not do that 😉

Thanks for your advice.I will notice that.😂😂😂

[mominshaikhdevs]

you can edit the quotes parts of your replies by just quoting the relevant lines. that way, this thread will become easier to read.

[Gaoyifei1011]

you can edit the quotes parts of your replies by just quoting the relevant lines. that way, this thread will become easier to read.

I have been mergeded it and remove duplicated comments.

[soroshsabz]

ITNOA

@ghost1372 Please add WinUI 3 Designer microsoft/microsoft-ui-xaml#5917 from #4710 to suggested plan

[ghost1372]

Done

[whiskhub]

Could you link the issue microsoft/microsoft-ui-xaml#4474 to the Application.RequestedTheme point?

[ghost1372]

Done

[pjmlp]

As I mentioned multiple times, when I still cared about WinUI / WinAppSDK, feature parity with WPF, including designer and at very least the same capabilities as System.Windows.Media, and for C++ development, the Visual Studio tooling that was dropped when C++/CX got replaced by C++/WinRT, and related talk at CppCon 2017.

But I doubt there are enough resources still around for any of this to matter, and I am quite curious how much WinUI still gets to be talked about at BUILD 2025, as the agenda seems quite empty into that regard.

[dotMorten]

It states windowing improvements above but just links to an issue about binding support on Window.
But what about finishing up window sizing, so we can do it in device-independent pixels and don't have to deal with screen scale, and tracking changes to screen scale ourselves?
I'd really like to see most of the AppWindow features graduate up to the WinUI Window class where they belong.

[ghost1372]

The cases mentioned are just a few, and it could include anything.
I added your case too.

[mominshaikhdevs]

[ghost1372]

Done!
Added a new Section for Titlebar

[MPITech]

I would love to see SVG compatibility throughout. DevExpress fully supported them in all their controls in WinForms, allowing our apps to look their best at all resolutions and scaling. It feels like a big step backwards in WinUI not being able to use SVG images everywhere that scale properly.

[whiskhub]

Agree, see microsoft/microsoft-ui-xaml#1494 for all the problems with icons.

[MPITech]

Agree, see microsoft/microsoft-ui-xaml#1494 for all the problems with icons.

Hahah, I actually made the last post in that thread when I first started with WinUI and saw what a mess icons were. I forgot about it.

[ghost1372]

added to list

[huoyaoyuan]

It's a bit late, but I'd like to highlight my pain points during development:

• Data binding/navigation stack support for NavigationView Proposal: Make NavigationView more friendly with data binding and implicit navigation microsoft-ui-xaml#5026. Every time when I use NavigationView I need to write a lot of ugly code for just simple functionality: map each navigation entry to a page, and map the selection state back when navigation is triggered by others.
• TextBox.InputBinding like WPF: I can't even find a clear way to do something when Shift+Enter is sent since modifier state tracking is different from UWP.
• DataTrigger for DataTemplate. It's extremely common to toggle some styles for items in list. It's also very common when DataTemplateSelector is too heavy and Converter is not extensible enough. DataTrigger is very easy to use. VisualStateManager only works for control template, not data template.
• Other minor control improvement like Proposal: Allow scrolling by index in ListView and GridView microsoft-ui-xaml#5069

Generally, the controls can be more friendly for data binding.

[Gaoyifei1011]

These are things we need and have been asking for years but have never been considered.

I hope Microsoft will consider this list. Also, if nothing is going to happen to any of the items, we expect a proper explanation so that we don't have to waste our time waiting to deal with it.

Instead of working on trivial things, focus on the following:

Controls

Name Remark
Splitter microsoft/microsoft-ui-xaml#5346
Inking Controls
DataGrid/TableView
PagerControl Available in all Experimental Releases but never released to Stable/Preview microsoft/microsoft-ui-xaml#60

Features/APIs

Name Remark
Kiosk Mode #3642
Windowing improvements Xaml Properties (Binding Support, Width, Height, Min/Max,...) microsoft/microsoft-ui-xaml#10358, Move AppWindow Stuffs to Window Class
AllowsTransparency microsoft/microsoft-ui-xaml#10311 (comment)
Input Validation microsoft/microsoft-ui-xaml#179
WinUI 3 XAML Designer microsoft/microsoft-ui-xaml#5917
Smooth App Resize microsoft/microsoft-ui-xaml#5148 (comment)
ApplicationData.GetForUnpackaged No ETA
AOT Support for Custom Control microsoft/microsoft-ui-xaml#10409 microsoft/microsoft-ui-xaml#10214
Custom Control Improvements Using xBind, Commands, AnccesstorType in ResourceDictionary, Improving TemplateBinding for using with Converters, microsoft/microsoft-ui-xaml#7003
ResourceDictionary Improvements Using xBind
Binding/xBind Improvements microsoft/microsoft-ui-xaml#2508 microsoft/microsoft-ui-xaml#560
Pin To Taskbar for UnPackaged Apps #3917
Non-XAML ThemeResource microsoft/microsoft-ui-xaml#10029
Drag and Drop support for Elevated Apps microsoft/microsoft-ui-xaml#7690
Add alternate label placement to ToggleSwitch microsoft/microsoft-ui-xaml#3696
Improved StorageFile APIs #8
Xaml Improvements microsoft/microsoft-ui-xaml#6569 microsoft/microsoft-ui-xaml#7037 microsoft/microsoft-ui-xaml#279 microsoft/microsoft-ui-xaml#929
Unseal all the things microsoft/microsoft-ui-xaml#780
Windows 10/11 Shell Context Menu #1082
Improve Cursor API (Change Mouse Cursor and More...) #1816 microsoft/microsoft-ui-xaml#506
Enable ItemsView selection via binding microsoft/microsoft-ui-xaml#10504
Enable Application.RequestedTheme at Runtime microsoft/microsoft-ui-xaml#4474 microsoft/microsoft-ui-xaml#2991
Splash screen microsoft/microsoft-ui-xaml#4055
Set x:Uid from Code-Behind microsoft/microsoft-ui-xaml#10575
SVG compatibility microsoft/microsoft-ui-xaml#1494

Bug Fix

Name Remark
Address top quality and experience issues
Slow Windows and Flickering microsoft/microsoft-ui-xaml#10259
Numberbox Rounding Issue
Application.RequestedTheme
Hyperlink Button not working with Uri like mailto:email microsoft/microsoft-ui-xaml#4438 microsoft/microsoft-ui-xaml#5630 microsoft/microsoft-ui-xaml#10448 microsoft/microsoft-ui-xaml#10428
Creating Window in App ctor microsoft/microsoft-ui-xaml#8664
Binding to bool shows Windows.Foundation.IReference`1 microsoft/microsoft-ui-xaml#4266
x:Bind does not work with C# record microsoft/microsoft-ui-xaml#5315

TitleBar Bug Fix

Name Remark
Title bar is stuck and not working https://github.com/microsoft/WindowsAppSDK/issues/5490
TitleBar title doesn't propagate to window microsoft/microsoft-ui-xaml#10557
Incorrect spacing when using a short title microsoft/microsoft-ui-xaml#10492
Resizing from top window border does not resize the contents with the new TitleBar control microsoft/microsoft-ui-xaml#10454
TitleBar control content misalignment and cropping after maximizing and dragging microsoft/microsoft-ui-xaml#10427
CenterContent in TitleBar control does not stretch properly microsoft/microsoft-ui-xaml#10421
TitleBar has too much whitespace in collapsed mode microsoft/microsoft-ui-xaml#10410
WinUI TitleBar - Resize behavior broken if TitleBar.IconSource is set microsoft/microsoft-ui-xaml#10374
Setting the maximize region of a win32 window using InputNonClientPointerSource secretly reverts back to default microsoft/microsoft-ui-xaml#10379
Setting the titlebar control back button visible through C# for the first time allows it to be dragged and removes animation microsoft/microsoft-ui-xaml#10350
TitleBar control calculation of padding is incorrect microsoft/microsoft-ui-xaml#10344
New TitleBar control with PathIconSource as IconSource breaks the app microsoft/microsoft-ui-xaml#9784
Double-click on XAML TitleBar icon doesn't close the window microsoft/microsoft-ui-xaml#9907
TitleBar doesn't respect AppWindow.TitleBar.IconShowOptions microsoft/microsoft-ui-xaml#9864
Cannot set color of Title and Subtitle text in TitleBar microsoft/microsoft-ui-xaml#9866
Cannot set the Background color of a TitleBar microsoft/microsoft-ui-xaml#9865
TitleBar doesn't respect AppWindow.TitleBar.PreferredHeightOption microsoft/microsoft-ui-xaml#9863
Tip

Completed features or fixes that have been implemented successfully.

Done

Name Remark
Picker Available in v1.8-exp1, Probably coming in v1.8, PR Merged
Appx/MsixBundle Probably coming in v1.8, Nuget Package Exist
App Freeze and Stop rendering in remote desktop Done 1 2 3

Where is Xaml2018? When will we enter the official version of the Windows App SDK (WinUI 3)?

--------------------------------

Xaml2018在哪里？什么时候进入到 Windows App SDK（WinUI 3）的正式版？

[ghost1372]

tnx, added to list