-
Notifications
You must be signed in to change notification settings - Fork 338
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] [L] Support for Windows WinUI 3 desktop apps #2673
Comments
Is this planned for 4.35.0? |
It's going to be investigated first. We need to understand what needs to be done, @igalfsg |
@jmprieur I haven't looked into the library's code. However, version 4.27.1 still works with Win UI 3. That was before it was switched from the in app prompt to browser authentication so I would guess it has something to do with how that feature was implemented. |
The same issue seems to be open in the Microsoft.UI.XAML repo I also tried using VS 2022 to build but I run into the same error |
This is most likely due to WinUI. MSAL has a tfm of |
I couldn't repro the bug. I created a Blank C# WinUI 3 app using the Windows App SDK 0.8.1, added the MSAL.NET library, and the project was built. I got an error that does not block the build. WinUI 3 supports arm64 and I guess MASL.NET doesn't: There was no runtime pack for Microsoft.WindowsDesktop.App.WindowsForms available for the specified RuntimeIdentifier 'win10-arm64'. |
Thanks @marb2000. Ill verify that I installed 0.8.1 and try again. |
I can confirm that the behavior still remains. I don't know if it's WinUI's issue to fix or the identity client. |
This is unlikely to be a Microsoft.Identity.Client problem. The error comes from a targets file introduced by WinUI
MSAL is a standard .NET library with a target on .net5-windows10.0.17763.0, which calls into WinRT APIs. |
I am not sure if this has been stated before but, I am able to use Microsoft.Identity.Client version 4.27.1 without issue in my WINUI 3 app. If I use a version later than that, I get an build error. It appears the issue was introduced in version 4.28.0, possibly. |
The issue should have been fixed @hachadwick , we're waiting for an SDK that has the fix to verify this. |
I appreciate the reply. I'll be looking for the updated SDK. |
Will this issue/ticket be closed when the SDK is updated? |
@bgavrilMS you can use 1.0.0-preview2 of the WinAppSDK, that has the fix and is publicly available now. |
@trwalke was looking into this, he'll can give it a go early next week. |
Need to do basic smoke testing to ensure new preview works |
This has come back now with MAUI in RC1: dotnet/maui#6052
|
This works today, there is nothing to do. |
@PaulSorauer-IPG Any luck? |
@diemperdiem - we expect this to work. Please open a new bug if it isn't. |
Should not be closed. This does not work if |
@rossirpaulo - please open a bug for this |
Here is the bug : #3941 |
The Microsoft.Identity.Client library doesn't support Windows WinUI 3 desktop Project Reunion apps today. I think the library is seeing the
net5.0-windows
TFM and thinking it's a WPF or WinForms app, and therefore doesn't work with a WinUI 3 app (which is neither of those).Describe the solution you'd like
Microsoft.Identity.Client library works with WinUI 3 desktop apps.
Additional context
To reproduce...
The text was updated successfully, but these errors were encountered: