-
Notifications
You must be signed in to change notification settings - Fork 11
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
Update to WinAppSdk 1.6, enable AoT on gallery head #195
Conversation
…to head, removed redundant RuntimeIdentifiers definition on libraries.
A local release/AoT build worked as expected the first time, but subsequent builds are giving this error message, even after a full and proper clean on the tooling repo:
I wonder if this could be related to our troubles in CommunityToolkit/Windows#169, considering the latest insights from 8.1-rc 🤔 |
@michael-hawker Locally, I've removed all usages of With AoT turned back on, we still get these errors:
edit: work on |
@Arlodotexe to double check, can you also try building against the latest CsWinRT build from the staging/AOT branch? You can just download the package from the artifacts (pick the latest commit from that branch) and setup a local feed for that. Also cc. @manodasanW for those generator errors. |
@Arlodotexe Can you set |
Here are the requested files: Animations.obj.Debug.zip |
Found the staging/AOT branch, but the DevOps feed is private. |
Thanks @Arlodotexe All 3 errors look related to our KeyVauluePair bug (microsoft/CsWinRT#1638) which is fixed for our next preview release.
|
Thanks @manodasanW, looks like that solved our issues on the library projects! The last remaining issue is on the app head:
Seems like a packaging error, |
I know we had a problem here we fixed with authoring WinRT components in C# that had this issue, but I don't think you are doing that here. In this scenario, .NET should have determined the newer version and picked that. I assume that CsWinRT package is from our feed that we had built in the pipeline right? I will probably need a binlog to investigate what is happening. Might want to also try clearing your bin / obj to see if that helps. |
That's correct @manodasanW, this is using CsWinRT |
@Arlodotexe Can you try out the preview we released yesterday. CsWinRT 2.1.0-prerelease.240722.1 https://github.com/microsoft/CsWinRT/releases/tag/2.1.0-prerelease.240722.1 |
Kicking the failed job, probably CommunityToolkit/Windows#347 again? |
I'm working on fixing all the AoT annotations locally before I dig into that too much. Cause might be related. |
@Arlodotexe I saw you had updated WindowsSdkPackageVersion to 38, you want to keep it on 37-preview until we address the type conflict issue in WinAppSDK. See my previous comment here. It is fine to increment the WinAppSDK version to preview1. |
I've got successful local builds with the latest changes, but CI in both CommunityToolkit/Windows#457 and CommunityToolkit/Labs-Windows#561 are throwing this:
We saw a similar error to this earlier, looks like our solution before was to update CsWinRT and the Windows SDK projection. @manodasanW anything you could add to this? |
Ah, I think I see why the build error is happening in the CI but not locally. The error is on the test head, not the gallery head. That's odd because we don't have AoT enabled on our test head, it's just the update to Wasdk 1.6 🤔 |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR: