-
Notifications
You must be signed in to change notification settings - Fork 345
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
[Bug] Cannot compile Windows MAUI .NET 9 project when referencing Microsoft.Identity.Client.Desktop #4993
Comments
we also have exsactly the same as usual a MAUI upgrade nightmare |
Same problem here. This is urgent since without that users aren't able to perform logins in my App |
Yep I don't have a solution yet still working on it
…On Fri, 15 Nov 2024, 19:30 nicop85, ***@***.***> wrote:
Same problem here. This is urgent since without that users aren't able to
perform logins in my App
—
Reply to this email directly, view it on GitHub
<#4993 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BBTUC66F7F7KX2MTOS33EC32AZDXFAVCNFSM6AAAAABRXBOE2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZZG43TMNZQG4>
.
You are receiving this because you commented.Message ID:
<AzureAD/microsoft-authentication-library-for-dotnet/issues/4993/2479776707
@github.com>
|
I don't think this is a .NET MAUI issue I was able to reproduce here on a WinUI app that doesn't use MAUI |
Thank you, |
Yes, still tracking down the exact culprit |
Thank you for your hard work.
Maxx Chloe Martin
IT
Elemel
…________________________________
From: Shane Neuville ***@***.***>
Sent: Wednesday, November 20, 2024 3:31:20 PM
To: AzureAD/microsoft-authentication-library-for-dotnet ***@***.***>
Cc: Maxx Chloe Martin ***@***.***>; Comment ***@***.***>
Subject: Re: [AzureAD/microsoft-authentication-library-for-dotnet] [Bug] Cannot compile Windows MAUI .NET 9 project when referencing Microsoft.Identity.Client.Desktop (Issue #4993)
Thank you, Do we think it's a .net 9 thing then?
Yes, still tracking down the exact culprit
—
Reply to this email directly, view it on GitHub<#4993 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BIRY2RSEMMY4BB7GCGQDLGL2BSTMRAVCNFSM6AAAAABRXBOE2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBYHA4TQMRTGU>.
You are receiving this because you commented.Message ID: ***@***.***>
Elemel 2018 CIC is a Community Interest Company registered in England and Wales with the registration number 11562022. We are authorised and regulated by The Office of the Regulator of Community Interest Companies. A list of the names of our members, together with a list of those persons who are designated as directors, is available for inspection at our registered office. The contents of this email, including any attachments, are strictly confidential and intended for the attention of the addressee only. In the event that you have received this email in error, please notify us and delete the message from your server. Our in-house antivirus software scans all outgoing emails before transmission, and no liability is accepted for any loss or damage caused by such email once it has been transmitted.
Elemel 2018 CIC is a Community Interest Company registered in England and Wales with the registration number 11562022. We are authorised and regulated by The Office of the Regulator of Community Interest Companies. A list of the names of our members, together with a list of those persons who are designated as directors, is available for inspection at our registered office. The contents of this email, including any attachments, are strictly confidential and intended for the attention of the addressee only. In the event that you have received this email in error, please notify us and delete the message from your server. Our in-house antivirus software scans all outgoing emails before transmission, and no liability is accepted for any loss or damage caused by such email once it has been transmitted.
|
i am also experiencing this issue. @PureWeen let me know if there's any information I can supply to aid your research. Thanks!
|
Thank you very much , for the info.
…On Fri, 6 Dec 2024, 09:45 Dimitris Iliopoulos, ***@***.***> wrote:
There is a workaround here <dotnet/maui#25883>
to bypass the issue. (Look into bug "Did you find any workaround?" section)
Here <dotnet/windowsdesktop#4789> they mention
they have resolved the issue and will be released in 9.0.1
—
Reply to this email directly, view it on GitHub
<#4993 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BBTUC6YUXCTBG5QSBESY64L2EFW3FAVCNFSM6AAAAABRXBOE2OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRSGY3TGMRVHE>
.
You are receiving this because you commented.Message ID:
<AzureAD/microsoft-authentication-library-for-dotnet/issues/4993/2522673259
@github.com>
|
Library version used
4.66.2
.NET version
.NET 9 MAUI
Scenario
Other - please specify
Is this a new or an existing app?
The app is in production, and I have upgraded to a new version of MSAL
Issue description and reproduction steps
Today we updated our MAUI app from .NET 8 to .NET 9.
Android and iOS are fine, but Windows does not work with the
Microsoft.Identity.Client.Desktop
package.The app cannot compile, showing these error messages:
Cannot resolve Assembly or Windows Metadata file 'Type universe cannot resolve assembly: System.Xaml, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089.'
and:
Could not copy the file "C:\temp\NET9MAUIWindowsIssue\obj\Debug\net9.0-windows10.0.19041.0\win10-x64\Platforms\Windows\App.xbf" because it was not found.
These errors also occur in a file->new->MAUI project, and only adding the package reference.
No code changed in the new MAUI app, only added the package reference.
See the example project in the attached zipfile:
NET9MAUIWindowsIssue.zip
Only the Desktop package is an issue, these packages work:
Relevant code snippets
Expected behavior
The app should compile (and work) on .NET9, like it also used to work on .NET8.
Identity provider
Microsoft Entra ID (Work and School accounts and Personal Microsoft accounts)
Regression
No response
Solution and workarounds
No solution or workaround as of yet.
The text was updated successfully, but these errors were encountered: