-
Notifications
You must be signed in to change notification settings - Fork 548
Handle frameworks and binding resource packages in Hot Restart #16605
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
Conversation
|
@microsoft-github-policy-service agree |
|
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
Looks like there is a build error going on |
|
Am I not allowed to use .NET 6 APIs? |
|
I added a BTW - The other approach I considered would be to not rely on these new symlink APIs but instead to re-implement the |
|
So there are a few problems here:
Yes, it's allowed, but...
No, not at the moment. We'll eventually get there, but we're not there yet.
Unfortunately there are a few problems here:
On the other hand I realize that zipped xcframeworks might contain symlinks that won't be needed (if they're for a different platform), so it certainly makes sense to find a solution here. However, given that implementing and testing this solution is likely to take a while, my suggestion would be to split this PR in two: one PR that only adds Hot Restart support for (xc)frameworks and binding resource packages, and then another one that tackles the symlink problem. From what you've done in this PR it looks like the first part would only contain changes to .props and .targets files, so that's much easier to test yourself (you can just change these files locally). |
|
OK, I will update this tomorrow and remove the zip changes. Indeed in my own library, we only have symlink in the maccatalyst target. The ios target has none, and the zip extract finds them just fine. Since only the ios target is needed for hot restart, I think it is fine to not support symlinks for now. |
|
Thanks! I'll have a look and see if I can write tests for this (and update the PR accordingly). |
|
Found and fixed a small but important bug with an extra trailing backslash, which was throwing off some subsequent checks such as creating the correct stamp file in the DynamicFrameworks folder. |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
✅ API diff for current PR / commitLegacy Xamarin (No breaking changes)
NET (empty diffs)
❗ API diff vs stable (Breaking changes)Legacy Xamarin (:heavy_exclamation_mark: Breaking changes :heavy_exclamation_mark:).NET (:heavy_exclamation_mark: Breaking changes :heavy_exclamation_mark:)✅ Generator diffGenerator diff is empty Pipeline on Agent |
💻 [PR Build] Tests on macOS M1 - Mac Big Sur (11.5) passed 💻✅ All tests on macOS M1 - Mac Big Sur (11.5) passed. Pipeline on Agent |
🚀 [CI Build] Test results 🚀Test results✅ All tests passed on VSTS: simulator tests. 🎉 All 223 tests passed 🎉 Tests counts✅ bcl: All 69 tests passed. Html Report (VSDrops) Download Pipeline on Agent |
|
@rolfbjarne can you take a second view on this. |
Yes, I'm working on adding tests for this scenario. |
dalexsoto
left a comment
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.
Awesome work! Once get the tests up we'll merge it! Thanks a lot @mattjohnsonpint ❤️
|
Thanks! Now if we can just #16001 fixed, we'll have all the iOS on Windows stuff working well. 🙂 |
Yep, I'm working on that one together with adding a test case for this issue. |
|
So I wrote a test for this scenario, and it revealed that this wasn't as simple as we first thought - in fact it was much more complicated. The good news is that I fixed all those issues, and the corresponding PR as been merged, so this PR is no longer needed (this means that xcframeworks and binding projects will finally work correctly with Hot Restart - but since the changes required were quite invasive, they won't be shipped until .NET 8. If you're willing to try a preview, they'll be available in the upcoming .NET 8 Preview 4). |
Updates the(removed per comment)Unziptask to properly create symbolic links, which may occur within resource zips containing xcframeworksFixes #16571
@rolfbjarne