WinAppSDK 1.7 Plans #4710
Replies: 70 comments 145 replies
-
|
Ability to pick WinUI3 / WindowsAppSDK app as a Kiosk app is a gap for me. Easy to do with UWP apps. Not possible with WinUI3 / WindowsAppSDK via Windows Settings. |
Beta Was this translation helpful? Give feedback.
-
|
This. As I approach finishing a kiosk mode for my in-production app I have no easy way to set up a kiosk as I did with the UWP app it is replacing. Very frustrating. Packaged Winui3 apps should have same single-app support as UWP apps. |
Beta Was this translation helpful? Give feedback.
-
|
Are there plans to stabilise the Compositor and Content Experimental APIs that have been in preview for some time? Also are there plans to make it possible to render with DWriteCore in D2D or Win2D? |
Beta Was this translation helpful? Give feedback.
-
I had posted a sample with DWriteCore/Direct2D (WinUI3_SwapChainPanel_DWriteCore) |
Beta Was this translation helpful? Give feedback.
-
|
As part of windowing improvements, we would really love to see a |
Beta Was this translation helpful? Give feedback.
-
|
Exactly what in my mind and about to log as a request. It's hard to keep track of the list of Windows. And a property to know the current Active Window too. |
Beta Was this translation helpful? Give feedback.
-
|
We need to set the app as owner of a new application window, to make it modal to avoid |
Beta Was this translation helpful? Give feedback.
-
|
Hi WinUI team, from my point of view (and my customers' point of view), you should implement input validation. That feature is crucial when deciding to use WinUI for line-of-business apps. Without input validation, the decision is usually against WinUI. Here is the corresponding issue: microsoft/microsoft-ui-xaml#179 |
Beta Was this translation helpful? Give feedback.
-
|
Lack of validation in WinUI is a black stain on WinUI's forhead. Input validation is a crucial building block of a UI framwork. |
Beta Was this translation helpful? Give feedback.
-
|
Coming from WPF it is baffling how something most basic and foundational like input validation is missing. Is this a legacy from Silverlight? Was UWP/WinUI 2 lacking input validation as well? |
Beta Was this translation helpful? Give feedback.
-
|
No, Silverlight had wonderful input validation. If I remember correctly |
Beta Was this translation helpful? Give feedback.
-
|
Oddly, that interface already exists in WinUI: Not sure how it's intended to be used though. |
Beta Was this translation helpful? Give feedback.
-
|
I actually handled that by creating a custom XAML form component, which works the same way EditForm in Blazor works and it works great. <forms:XamlForm
Command="{x:Bind ViewModel.LoginCommand, Mode=OneWay}"
Model="{x:Bind ViewModel, Mode=OneWay}"
Validator="{x:Bind Validator}">
<StackPanel Padding="20,5" Spacing="7">
<forms:XamlFormField forms:XamlForm.Field="Email">
<TextBox
Margin="3,2"
IsEnabled="{x:Bind ViewModel.IsLoginModeOnly, Mode=OneWay, Converter={StaticResource InverseBoolConverter}}"
PlaceholderText="Email/Username"
Text="{x:Bind ViewModel.Email, Mode=TwoWay}" />
</forms:XamlFormField>
<forms:XamlFormField forms:XamlForm.Field="Password">
<PasswordBox
Margin="3,2"
Password="{x:Bind ViewModel.Password, Mode=TwoWay}"
PlaceholderText="Password" />
</forms:XamlFormField>
<StackPanel Orientation="Horizontal">
<Button
MinWidth="150"
Padding="10,5"
VerticalAlignment="Stretch"
forms:XamlForm.IsSubmit="True"
IsEnabled="{x:Bind ViewModel.IsLoggingIn, Mode=OneWay, Converter={StaticResource InverseBoolConverter}}"
Style="{StaticResource AccentButtonStyle}">
</Button>
...
</StackPanel>
</StackPanel>
</forms:XamlForm>
|
Beta Was this translation helpful? Give feedback.
-
|
This one from the 1.6 plans Mike! @codendone.
|
Beta Was this translation helpful? Give feedback.
-
|
Can you transcribe that or link to it? Reading that image is difficult. |
Beta Was this translation helpful? Give feedback.
-
|
Yes of course! @riverar The original post I hope this message finds you well. As I explore the capabilities of WinAppSDK, I've identified a usability concern related to ContentDialogs, especially when utilized for data entry. Due to the fixed positioning, the inability to drag and reposition these dialogs limits their flexibility and prevents users from viewing the content beneath them. Best regards, Thank You! 😄 @codendone Answer Thanks for your feedback, @horaciodiez. Yes, improved dialog capabilities, including those you mention, is something we'd like to make easier and maybe even default. |
Beta Was this translation helpful? Give feedback.
-
|
Sweet, thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Another option (which may be preferrable in some cases) is the possibility to create a "modal" Window, so that the user can interact only with the new Modal Windows, until it is closed. This type of window should appear just like any other window (so, it is very different appearance from ContentDialog). An example is provided by Visual Studio: the Options Window behavior is what I would get. I had tried to build it, but no success (here the details). |
Beta Was this translation helpful? Give feedback.
-
|
Implement a set of pickers with capabilities like those in Windows.Storage.Pickers, but are actually usable in appcontainers and when running as administrator. |
Beta Was this translation helpful? Give feedback.
-
|
If I get it right, it is this issue: dotnet/maui#23787 (comment) and that's the one issue that prevents us from moving to use the unpackaged mode for our app (@jonathanpeppers had the same experience). Note that MAUI app on Windows will use the unpackaged mode by default in .NET 9+. tl;dr: Unpackaged MAUI apps crash when one opens a file picker and the user is logged in as administrator (!). |
Beta Was this translation helpful? Give feedback.
-
|
I can't upvote this enough: #2504 |
Beta Was this translation helpful? Give feedback.
-
|
It seems some work has started for the picker. |
Beta Was this translation helpful? Give feedback.
-
|
I hope to see the TitleBar in the next version 1.6.1 |
Beta Was this translation helpful? Give feedback.
-
|
I missed the last part of the call, but do I see a WinUI vs designer coming ? |
Beta Was this translation helpful? Give feedback.
-
|
Yes |
Beta Was this translation helpful? Give feedback.
-
|
No news there, but Microsoft India Development Center (IDC) is exploring the capability. |
Beta Was this translation helpful? Give feedback.
-
|
The designer needs to be top priority if WinUI3 is to replace Winforms! |
Beta Was this translation helpful? Give feedback.
-
|
I'd love to see you guys actually focus on clearing the backlog of bugs. You purged thousands of issues people had put time into diagnosing and documenting and I can see the same thing happening again. You guys are leagues behind AppKit/UiKit and even Android feels less buggy than WinUI. Focus on paying down some of the bugs rather than shiny things. Also it would be great to see input validation addressed (microsoft/microsoft-ui-xaml#179), it's a huge issue to port a large LOB from WPF without this. |
Beta Was this translation helpful? Give feedback.
-
|
Add native BlazorWebView control for WinUI. There is support for WinForms and WPF, why not WinUI? Current workaround via MAUI embedding is definitely an overhead. Adds too many dependencies for a single control. |
Beta Was this translation helpful? Give feedback.
-
|
Agree. Biggest oversight from MS not to support BlazorWebView in WinUI as it will immediate help unifying the WinUI ecosystem with Blazor making it more attractive to invest. |
Beta Was this translation helpful? Give feedback.
-
|
Fix Not Implemented Exception in UWP for Image.Resize. Multiple errors trying to Publish an app to UWP that references a MAUI Class Library. |
Beta Was this translation helpful? Give feedback.
-
|
@codendone what happened to UWP-like "Smooth App Resize" feature/(microsoft/microsoft-ui-xaml#5148, microsoft/microsoft-ui-xaml#2506) that were previously part of WASDK 1.7 roadmap?
|
Beta Was this translation helpful? Give feedback.
-
|
Without that apps look like a kids project. |
Beta Was this translation helpful? Give feedback.
-
|
Please fix this NumberBox issues like false rounding floating point numbers and implement the exponential notation. |
Beta Was this translation helpful? Give feedback.
-
|
And let us open a file dialog at a custom folder, not only at downloads, pictures.. |
Beta Was this translation helpful? Give feedback.
-
|
The thing is, there are dialogs that allow you to set this. Both the Common Dialog Box library and the Common Item Dialog both allow you to set this. While I linked to the C++ documentation, .NET wraps the Common Dialog Box library in its dialog library. |
Beta Was this translation helpful? Give feedback.
-
|
@DarranRowe I am using WinApp SDK with winrt/c++. I tried this Common Item Dialog and this fixes the start path. But sure, I don't want to use this old win32 api Stuff. |
Beta Was this translation helpful? Give feedback.
-
|
Can we have an ability to delay the registration of appinstaller and delay the de-registration of removals of msix packages from the system if the packages are in use? |
Beta Was this translation helpful? Give feedback.
-
|
When Win2d full support for WinUi3 will be ready? |
Beta Was this translation helpful? Give feedback.
-
|
What are you missing? |
Beta Was this translation helpful? Give feedback.
-
|
Interop with DirectX. No memory leaks. Performence etc.. |
Beta Was this translation helpful? Give feedback.
-
|
I only had as issue with a meamory leak what i colud solve usinge the CanvasControl function Device().Trim(); |
Beta Was this translation helpful? Give feedback.
-
|
Better to never run the app as an administrator at all. You can work
around that by using impersonation to increase admin privileges for that
thing when you run it.
But, if you do,
You can check the login of the user and, if they are an administrator or
being run as an administrator, then you can make them sign into Windows and
get credentials for the store anyway.
…On Thu, Mar 13, 2025 at 4:40 AM Denis Osipov ***@***.***> wrote:
Need ability to purchase Addons (In-App purchases)
StoreProduct.RequestPurchaseAsync
<https://learn.microsoft.com/en-us/uwp/api/windows.services.store.storeproduct.requestpurchaseasync?view=winrt-26100#windows-services-store-storeproduct-requestpurchaseasync>
when WinUI3 app run as Administrator. This is critical business issue right
now.
Also need Picker and Print support when run as Administrator.
—
Reply to this email directly, view it on GitHub
<#4710 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGWTEMB5HM5BNN6DKRHTZZT2UFG7ZAVCNFSM6AAAAABOBJPCESVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENBYGU4DCNY>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
How about they fix what is basic windows functionality since ages ago. |
Beta Was this translation helpful? Give feedback.
-
|
Are there any plans to include Windows App SDK modules in the exe file when publishing a native AOT deployment? |
Beta Was this translation helpful? Give feedback.
-
|
@codendone
*. Available from AppWindow and Not XAML All these users deserve at least a full explanation for all this lack of planning and commitment. |
Beta Was this translation helpful? Give feedback.
-
|
If 1.7 is officially released, would anyone know if WebAuthenticator is finally working in UWP? Official documentation still shows "not supported" |
Beta Was this translation helpful? Give feedback.
-
@solomonfried Frustratingly, they have a completely new |
Beta Was this translation helpful? Give feedback.
-
|
These are things we need and have been asking for years but have never been considered.
|
Beta Was this translation helpful? Give feedback.
-
|
Numberbox rounding issues and not being able to bind to anything but double without using a converter is killing us. But I agree with most of this list. Microsoft said WinUI was the way to go for Windows desktop apps, but how can any serious application not be able to bind a numberbox to a decimal (currency) value natively without possible rounding issues? Some of these things have been around so long, it's almost incredible that they are still outstanding. I am starting to think I may have made the wrong decision to go with WinUI for our large application. I wish someone would prove me wrong. |
Beta Was this translation helpful? Give feedback.
-
|
@ghost1372 feels like a dead horse, use wpf for windows and else blazor |
Beta Was this translation helpful? Give feedback.
-
|
@ghost1372 I will suggest that you create a mega issue in this repo that merges issues from #4710 (comment) + #4710 (comment) + #4710 (comment)? That way, we will have a mega issue that will list all the issues in one place and it will be easier for devs to monitor the progress. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
We also need splitter control, I'm waiting for many years |
Beta Was this translation helpful? Give feedback.
-
|
@shelllet While not native controls, have you checked out Windows Community Toolkit's splitter and sizer control options? It may have what you need in the meantime.
|
Beta Was this translation helpful? Give feedback.
-
|
That's a good suggestion, but it's only for .NET applications. If you're using C++/WinRT, there's still no splitter alternative |
Beta Was this translation helpful? Give feedback.
-
Your list is the list of every developper. I stop wainting microsoft and go to avalonia because an app without input validation is impossible in busisnes and mission critical software. Avalonia has input validatio, has designer, and also has aot and even kiosk (with powershell instalation and appx packaging) |
Beta Was this translation helpful? Give feedback.
-
|
@codendone Colleagues, we really need the InkCanvas component. We've been waiting for it for a long time and cannot migrate from UWP. I noticed that InkCanvas was present in the recent Microsoft.WindowsAppSDK 1.7.250109001-experimental2, but after yesterday's release of 1.7.250310001, I couldn't find it there. When do you plan to release this component? |
Beta Was this translation helpful? Give feedback.
-
|
The code for that inkcanvas is basically unusable, and it has not been updated for 8 months. He mainly encapsulated inkdesktop host and there is nothing else. Then, due to being two window handles, there were also event triggers and rendering events that affected the control. |
Beta Was this translation helpful? Give feedback.
-
|
@duwenlong2 did you ever come around to finding an alternative to this? I'm currently trying to find a replacement for this control in an app being migrated from UWP to WinUI3... |
Beta Was this translation helpful? Give feedback.
-
|
Two basic things missing, if you can prioritize -
|
Beta Was this translation helpful? Give feedback.
-
|
You can do toast notifications with this |
Beta Was this translation helpful? Give feedback.
-
|
The notification in this variant, as adopted in SDK by UWP, does not really make sense. See my article on this: You can only use the current SDK notification to send an instant message to windows. This can be done with pretty much all UI libraries within the app, I don't need to take the route via Windows OS! But the main task of a notification should be the scheduled notification and unfortunately SDK can't do that, because there only show method was adopted from UWP! Regards |
Beta Was this translation helpful? Give feedback.
-
|
SCHEDULED LOCAL NOTIFICATION As @amitchaudhary has already written (I hope he was thinking of the local notification), please be sure to implement the method for the Scheduled Notification! The notification as it is now in the SDK makes (as I have often written) absolutely no sense! You can find more information about this topic here: #5046 The current workaround is via UWP Nuget (Microsoft.Toolkit.Uwp.Notifications). Besides, you shouldn't use this Nuget in MAUI at all, I don't think it will be updated (last update in 2022). However, the problem with this UWP solution is that no ID is passed by Windows OS because the OnActivated event does not exist in MAUI! Thanks |
Beta Was this translation helpful? Give feedback.
-
|
TableView must become a priority, because its absence leaves LOB apps out in the cold. While there are third-party grids, all have additional features like filters, export, which are totally redundant. A slim, simple, performant read-only table view is a must have. WCT started something based on ListView, but it hasn't been touched for two years already. |
Beta Was this translation helpful? Give feedback.
-
|
You may have something you use temporarily while were waiting for MS, im using this TableView, its very good. |
Beta Was this translation helpful? Give feedback.
-
|
DataTemplate.Triggers like in WPF is really needed. |
Beta Was this translation helpful? Give feedback.
-
|
It's been nine months since we last talked about the designer, can you reveal the progress of the development so far? |
Beta Was this translation helpful? Give feedback.
-
|
inkcanvas please! |
Beta Was this translation helpful? Give feedback.
-
|
Btw So much silence... Another dead UI Tech by MS? |
Beta Was this translation helpful? Give feedback.
-
|
It freaking sucks to be dependent on MS technology |
Beta Was this translation helpful? Give feedback.
-
|
Visit the 1.8 suggested plan discussion, this discussion is dead because 1.7 is released |
Beta Was this translation helpful? Give feedback.
-
|
Let's be honest MSFT, your current UI framwork strategy for .NET is a complete mass. MSFT should have unified the MAUI and WinUI team into a single team/framework from the beginning, right when they started creating them. In my vision, WinUI was supposed to be the SINGLE UNIFIED MULTIPLATFORM UI framework for .NET developers. Having multiple teams trying to create multiple UI frameworks it's nothing but making the .NET community to gets less and less confident about picking any o them because we're sure that both MAUI and WinUI will be eighter buggy or missing the basic controls that you need working solid rock. So MSFT should really go back to it's drawing board and completely rethink it's UI framework products. What I would suggest it's to eighter merge MAUI team into the WinUI or the other way around, and put all of them to evolve one of these 2 frameworks to be a rock solid multiplatform product. I would even risk to suggest to pick WinUI as the one to be the single UI framwork solution so Windows will be truly threaded as the first citizen of it. The current fragmented set of UI Frameworks from MSFT has been failing hard to get a broad developer community adoption because MSFT it's not investing enough on it, and the current small investment it's also being wrongly used because of this UI frameworks fragmentation. |
Beta Was this translation helpful? Give feedback.
-
|
I'm ok if you don't like my tone (I'll try to improve myself on this sense), but which exactly of my claims above do you think it's incorrect?
So what do you think it's incorrect here? Really, I'm just trying to learn with someone more experienced in XAML then me... |
Beta Was this translation helpful? Give feedback.
-
|
WinUI is short for "Windows UI", why would they make that cross-platform? Plus, .NET MAUI already uses WinUI 3 on Windows |
Beta Was this translation helpful? Give feedback.
-
|
I know WinUI stands for "Windows UI", the naming doesn't matter, what really matter it's the UI side of .NET being too fragmented like it is right now. They could have named it as simple as ".NET UI" and merge the 2 project's and team's effort around a single multiplatform XAML based framework for .NET developers. |
Beta Was this translation helpful? Give feedback.
-
|
My point here is that, I haven't seen almos any company that's currently interest to develop a native app for Windows only. I believe that if Microsoft merged the 2 teams to work on a single .NET UI framework that works seamless on Windows, more apps will be created also for Windows and published on Windows Store. Nowadays, with the inferior support that MAUI has for Windows, almost any company that's developing native apps using MAUI it's interested in Windows because when they bump into bugs that I've bumped into, the companies usually just say: "f*ck Windows, if it's causing problems, just remove it from our app and move on with Android and iOS. Cause for desktops they always have a Web version of the same app to use on Desktop. Some of you might disagree with all that I've said, but it is what it is... |
Beta Was this translation helpful? Give feedback.
-
What about C++ developers? Are you stating here that C++ developers have to take a dependency on .NET in order to use WinUI? |
Beta Was this translation helpful? Give feedback.
-
|
So What is the future PLAN for WinUI 3? |
Beta Was this translation helpful? Give feedback.
and others
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We're currently early in the planning for Windows App SDK 1.7, but here are some of the top-of-mind improvements we're looking at:
We'll need to report back when we complete our 1.7 planning.
Please use this discussion to provide feedback on these top-of-mind improvements, or to provide feedback and up-votes on other features and issues we should prioritize.
Beta Was this translation helpful? Give feedback.
All reactions