WinAppSDK 1.7 Plans #4710
Replies: 76 comments 169 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.
-
|
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.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Minimizing to system tray is trivial with win32 interop. Annoying? Yes. But hardly a show-stopper. Lack of kiosk support is much higher priority in my opinion. |
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.
-
|
Follow this |
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.
-
|
This is the latest post in the announcements channel. |
Beta Was this translation helpful? Give feedback.
-
I mean what's the plan other than bug fixes and AI features. |
Beta Was this translation helpful? Give feedback.
-
Bug: Scrolling Not Working for Synaptics Touchpad in WinUI 3Summary: Hardware & Environment Details
DescriptionWhen using a Synaptics Touchpad, scroll gestures (two‑finger vertical/horizontal scroll, edge scroll) do not work in WinUI 3 apps. Expected BehaviorScrolling gestures on the Synaptics Touchpad should work in WinUI 3 apps exactly as they do in WinUI 2/UWP apps. Actual Behavior
Steps to Reproduce
Additional Notes
|
Beta Was this translation helpful? Give feedback.
-
|
If @dotMorten is not comfortable with this as it is created here, vote or comment to remove/delete this thread from here. 🤔 |
Beta Was this translation helpful? Give feedback.
-
|
I don’t follow? Why wouldn’t you just log this as an issue rather than as a comment on an already released version? |
Beta Was this translation helpful? Give feedback.
-
|
@m-asadullah what does "being comfortable" have to do with anything? Do you want the issue solved or don't you? Making it visible as a real issue is how open source projects work. You could of course add a reference to the issue here afterwards but nobody's going to work on it if it only exists here. |
Beta Was this translation helpful? Give feedback.
-
|
@m-asadullah 
Otherwise your hard-worked homework you invested in created your comment will go in vain. |
Beta Was this translation helpful? Give feedback.
-
|
While this may not be the conventional place to report bugs, this topic directly relates to the Plans for future development. Planning cannot be effective without:
The combination of
Despite the volume, many issues appear to be closed without resolution or meaningful follow-up. To ensure visibility, @cdock1029 this concern is being raised here in the Discussions section, where responses tend to be more active and community-driven. The issue of touchpad scrolling not working has been repeatedly reported since 2020, forming a chain of related cases across repositories—many closed without resolution, including one reopened with its last comment in April 2025.🔗. In this discussion asked last year when experienced the problem... ... but answer by @dotMorten not satisfied and waiting for 1.8 stable release. @weitzhandler, this is referenced in issue created but now closed after being resolved. #10767
|
Beta Was this translation helpful? Give feedback.
-
|
New Outlook is using a WebView2 with Fluent UI Web, but native WINUI3 so for UI. Best regards. |
Beta Was this translation helpful? Give feedback.
-
|
I understand your concern, but I don’t think Microsoft is abandoning WinUI — it’s more about a hybrid strategy.
The market has shifted: users now expect apps that work everywhere and keep their data in sync across devices. Web technologies are simply the fastest way to achieve that. For us developers, it’s not “WinUI vs Web” but “WinUI and Web.” Native skills remain valuable, but adding web/cross-platform knowledge makes us more adaptable to today’s customer needs. pc |
Beta Was this translation helpful? Give feedback.
-
|
Microsoft is crazy lost. Their speech about "multiple dev stack choices" is hilarious and fully contradictory.
Consistency wise, It just doesn't make any sense. |
Beta Was this translation helpful? Give feedback.
-
|
You bring it to the point. |
Beta Was this translation helpful? Give feedback.
-
|
@ederbond I feel like you're making it sound worse than it is rather than looking at it as a natural evolution. WPF came before Silverlight, and they each targeted different scenarios, and almost completely identical in how XAML works. Win8/UWP/WinUI are essentially all the same UI Framework, with WinUI being the change asked for by the community. IMHO there were just 2 XAML stacks: One outdated one based on DirectX 9 and slow performance, and a modern DX11 version with compiled bindings and other enhancements. Both of them are still fully supported and maintained today. |
Beta Was this translation helpful? Give feedback.
-
|
He was wrong about the specifics but right about the general path. And he also fogot to add LightSwitch and Maui. |
Beta Was this translation helpful? Give feedback.
-
|
Since this discussion is still active and TableView has been mentioned in it, those who have been waiting for TableView since it first appeared in the 1.5 roadmap, they can take a look at WinUI.TableView. It’s fluent, fast, and feature-rich, , and also supports Uno Platform. Even more features are coming soon, check out the roadmap for v1.4 and feel free to provide your valuable feedback.
|
Beta Was this translation helpful? Give feedback.
-
|
Any change it could bring support for .NET MAUI ? |
Beta Was this translation helpful? Give feedback.
-
|
not though about it yet, but someone is already using it in their MAUI project. |
Beta Was this translation helpful? Give feedback.
-
|
Just out of curiosity, what do you need for Kiosk support besides full
screen?
…On Sun, Sep 28, 2025 at 3:54 PM Christopher Carmichael < ***@***.***> wrote:
Minimizing to system tray is trivial with win32 interop. Annoying? Yes.
But hardly a show-stopper. Lack of kiosk support is much higher priority in
my opinion.
—
Reply to this email directly, view it on GitHub
<#4710 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGWTEMFW5C4GS6K2P3K6DI33VBDHRAVCNFSM6AAAAABOBJPCESVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINJTGYYDGOA>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
Beta Was this translation helpful? Give feedback.
-
|
Changes to Windows itself to allow packaged desktop applications to be usable as kiosk applications. |
Beta Was this translation helpful? Give feedback.
-
|
I’ve been waiting since MAUI first shipped for WebAuthenticator to work on Windows. Unfortunately, it still doesn’t. Calling WebAuthenticator.AuthenticateAsync on Windows just throws a NotSupportedException. From what I can tell, the roadblock isn’t MAUI itself but the Windows App SDK. Without deeper changes there, MAUI can’t enable the feature. There are a few GitHub issues tracking this (#2702 For now, the only options are workarounds like WinUIEx 👉 If you’ve spotted movement on this—maybe a PR or milestone update—please share. I know a lot of us are waiting on this one. |
Beta Was this translation helpful? Give feedback.
-
|
I did a PR for Maui with some outstanding questions. Winappsdk has (the bare minimum of) what is needed for Maui to complete this work |
Beta Was this translation helpful? Give feedback.
-
|
Is there any way to tell if it is being worked on? |
Beta Was this translation helpful? Give feedback.
-
|
I didn't want to give up external identity provider login in Windows, so I implemented it via the web. I generate a unique ID and send it to WebApi/IDP. IDP verifies the user and sends me back the ID, which I then store. I use a pooling query on the client to constantly check whether the entry for the ID exists (e.g., max. 15 seconds). I must admit that this approach is somewhat unusual and pragmatic, but since I develop cross-platform (MAUI Blazor Android, iOS, Mac, Windows + Web (Blazor Server)), I use the same logic on all platforms and, more importantly, it works everywhere and always. pc |
Beta Was this translation helpful? Give feedback.
-
|
@true-perfect-code Interestingly, ChapGPT officered this solution, which I haven't tested but I assume won't work. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, with MAUI, a separate browser must be opened. The idea is to use the same workflow for external ID provider registration as you would for an web application. AI can perform very well when it comes to limited and well-defined areas. In this case, I think you'll lose more time with AI than if you did it yourself. Here's my workflow with MAUI:
As you can see, this request runs for a maximum of 15 seconds on the MAUI client. During this time, a confirmation must be available on the DB server, otherwise the login was not successful. The rest on the WebApi server is exactly the same as if you were performing web authentication. Once again: This is not a standardized procedure, but I saw no other way to implement it on MAUI due to the Microsoft authenticator. Of course, you can only do this with Microsoft idP and then use the usual method recommended for others (Android/iOS), but the appeal of this approach is that I have the same structure for both my web and MAUI solutions, and that's with all three providers. Furthermore, this will continue to function for the next 10-20 years because web apps will exist and they will need to be authenticated in this manner. The only disadvantage is that the user sees the browser after the redirection, and of course you have to give them the information when authentication is successful so that they can close it. This can be done very easily from Program.cs (WebApi ASP.NET minimal API), for example): And then minimal API: pc |
Beta Was this translation helpful? Give feedback.
-
|
And you can tell that MS must use a similar approach, because, that's what
github integration with Visual Studio does. There's a web page that does
the auth. Now if you really wanted to get hardcore, I suppose you could
build your own form that drives a webview under the hood, but, that is
"fraught with danger".
…On Tue, Sep 30, 2025 at 2:03 AM true-perfect-code ***@***.***> wrote:
@solomonfried <https://github.com/solomonfried>
Yes, with MAUI, a separate browser must be opened. The idea is to use the
same workflow for external ID provider registration as you would for an web
application.
AI can perform very well when it comes to limited and well-defined areas.
In this case, I think you'll lose more time with AI than if you did it
yourself.
Here's my workflow with MAUI:
- First define the Satet, e.g., GUID, to identify which IDP it is and
which platform the user comes from (the last one is for statistical
reasons) => *var stateData =
$"{deviceTypePlatform}|{LoginModel.Idp}|{pollingId}";*
- then merge WebApi url => *var authUrl =
$"{_globalState.WebApiUrl}/auth/external?state={Uri.EscapeDataString(stateDataBase64)}";*
- Then you can open your browser and submit the URL (if shared code
due to MAUI Blazor and Blazor Server, then via interface with different
platform-specific implementations). => *await
_platform!.AuthenticateAsync(authUrl);* *Note: With MAUI, you can use
await Launcher.Default.OpenAsync(authUrl); at this point; with web, I
simply use NavigateTo.*
- The last MAUI step after sending the request to WebApi is to pool
the DB to find out whether a confirmation from Google/Apple or Microsoft
has arrived there. You can do this using a simple loop, e.g.:
for (int i = 0; i < maxSeconds; i++)
{
cancellationToken.ThrowIfCancellationRequested(); // Prüfe Abbruchanforderung
await Task.Delay(1000, cancellationToken);
pE.Services.Dam.ClientStorageModel result_idptoken = await _dam!.GetTokenIDP(db_para);
if (result_idptoken != null && !string.IsNullOrEmpty(result_idptoken.WebApiToken))
{
result = result_idptoken;
break;
}
}
As you can see, this request runs for a maximum of 15 seconds on the MAUI
client. During this time, a confirmation must be available on the DB
server, otherwise the login was not successful.
The rest on the WebApi server is exactly the same as if you were
performing web authentication.
Once again: This is not a standardized procedure, but I saw no other way
to implement it on MAUI due to the Microsoft authenticator. Of course, you
can only do this with Microsoft idP and then use the usual method
recommended for others (Android/iOS), but the appeal of this approach is
that I have the same structure for both my web and MAUI solutions, and
that's with all three providers. Furthermore, this will continue to
function for the next 10-20 years because web apps will exist and they will
need to be authenticated in this manner. The only disadvantage is that the
user sees the browser after the redirection, and of course you have to give
them the information when authentication is successful so that they can
close it. This can be done very easily from Program.cs (WebApi ASP.NET
minimal API), for example):
events.OnCreatingTicket = async context =>
{
.....
context.Properties.Items["jwt"] = jwt;
context.Response.Redirect("/auth/close-browser");
await Task.CompletedTask;
};
And then minimal API:
app.MapGet("/auth/close-browser", async (HttpContext context) =>
{
// Generiere das HTML für die "Tab schließen"-Seite
var htmlContent = @"
<!DOCTYPE html>
<html lang=""de"">
<head>
<meta charset=""UTF-8"">
<meta name=""viewport"" content=""width=device-width, initial-scale=1.0"">
<title>Authentifizierung abgeschlossen</title>
<style>
body {
font-family: Arial, sans-serif;
display: flex;
flex-direction: column;
justify-content: center;
align-items: center;
min-height: 100vh;
margin: 0;
background-color: #f0f2f5;
color: #333;
text-align: center;
}
.container {
background-color: #fff;
padding: 40px 30px;
border-radius: 8px;
box-shadow: 0 4px 15px rgba(0, 0, 0, 0.1);
max-width: 500px;
width: 90%;
}
h1 {
color: #28a745; /* Grüne Farbe für Erfolg */
margin-bottom: 20px;
}
p {
font-size: 1.1em;
line-height: 1.6;
margin-bottom: 30px;
}
.logo {
margin-bottom: 20px;
/* Wenn ein Logo, dann hier einbinden */
/* Beispiel: img src=""/path//logo.png"" alt=""App Logo"" style=""max-width: 150px;"" */
}
.instructions {
font-weight: bold;
color: #555;
}
</style>
</head>
<body>
<div class=""container"">
<div class=""logo"">
</div>
<h1>Authentication successful!</h1>
<p>
You have been successfully logged in. Your token has been transferred to the application.
</p>
<p class=""instructions"">
You can now close this browser window.
</p>
</div>
<script>
// Optional: Versuch, das Fenster automatisch zu schließen.
// Beachte: Browser-Sicherheitseinstellungen können dies verhindern,
// wenn das Fenster nicht von einem Script geöffnet wurde.
// Ein expliziter Hinweis ist daher immer am besten.
// try {
// window.onload = function() {
// setTimeout(function() {
// window.close();
// }, 2000); // Versuch, nach 2 Sekunden zu schließen
// };
// } catch (e) {
// console.error('Auto-close failed:', e);
// }
</script>
</body>
</html>";
// Setze den Content-Type auf text/html, damit der Browser es als HTML rendert
context.Response.ContentType = "text/html";
await context.Response.WriteAsync(htmlContent);
});
pc
—
Reply to this email directly, view it on GitHub
<#4710 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGWTEMBTQKL5GUDMOYXBX7T3VITKZAVCNFSM6AAAAABOBJPCESVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINJUHEZDSMI>
.
You are receiving this because you commented.Message ID:
***@***.***
com>
|
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