fix(net8): Adjust WinUI property detection#13700
Conversation
.NET 8 changes the ordering of nuget defined props files, This change makes WinUI detection independent of nuget props import and rely on .targets evaluation.
|
The build 94727 found UI Test snapshots differences: Details
|
|
@jeromelaban does this need a backport? |
|
@jeromelaban How can I use this fix, I tried to install preview packages but I got the same error. |
|
@tibitoth this has been release in the latest build of 4.10.x. If you're still having issues, make sure to open a discussion. |
@jeromelaban, I apologize for asking, but what about version 5.0.0-dev.****? |
|
@limeniye can you open a discussion with more details, this is already on 5.0-dev builds. Thanks! |
|
My bad. Was successfully fixed. Off topI confused it with the RuntimeIdentifiers problem. |

GitHub Issue (If applicable): closes #13678
PR Type
What kind of change does this PR introduce?
What is the new behavior?
.NET 8 changes the ordering of nuget defined props files, This change makes WinUI detection independent of nuget props import and rely on .targets evaluation.
Copilot Summary
🤖 Generated by Copilot at 591797b
Moved the import of
uno.winui.common.propsto the targets file and added a check for WinAppSDK projects. This fixes a bug where WinUI projects using WinAppSDK were not recognized by Uno.PR Checklist
Please check if your PR fulfills the following requirements:
Screenshots Compare Test Runresults.Other information
Internal Issue (If applicable):