-
Notifications
You must be signed in to change notification settings - Fork 834
fix: Fix cannot HR app with project dependency with code and rider #21921
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
...UI.RemoteControl.Server.Processors/HotReload/MetadataUpdates/CompilationWorkspaceProvider.cs
Outdated
Show resolved
Hide resolved
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.
Pull request overview
This PR fixes a hot reload issue where applications with project dependencies targeting different target frameworks (TFMs) could not be hot reloaded in VS Code and Rider. The fix follows the same pattern already established for RuntimeIdentifier handling.
Key Changes:
- Apply
TargetFrameworkonly to the head project during hot reload, not transitively to all referenced projects - Use temporary property
UnoHotReloadTargetFrameworkto avoid forcing TFM globally
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| src/Uno.UI.RemoteControl.Server.Processors/HotReload/ServerHotReloadProcessor.MetadataUpdate.cs | Removes TargetFramework from global properties and stores it as UnoHotReloadTargetFramework during hot reload workspace initialization |
| src/Uno.UI.RemoteControl/buildTransitive/Uno.WinUI.DevServer.props | Restores UnoHotReloadTargetFramework back to TargetFramework conditionally for projects that reference the Dev Server assembly |
src/Uno.UI.RemoteControl.Server.Processors/HotReload/ServerHotReloadProcessor.MetadataUpdate.cs
Outdated
Show resolved
Hide resolved
src/Uno.UI.RemoteControl.Server.Processors/HotReload/ServerHotReloadProcessor.MetadataUpdate.cs
Outdated
Show resolved
Hide resolved
Co-authored-by: Copilot <[email protected]>
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.
Pull request overview
Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.
|
🤖 Your WebAssembly Skia Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-21921/wasm-skia-net9/index.html |
|
🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-21921/docs/index.html |
|
The build 184511 found UI Test snapshots differences: Details
|
|
@Mergifyio backport release/stable/6.4 |
✅ Backports have been createdDetails
|
…6.4/pr-21921 fix: Fix cannot HR app with project dependency with code and rider (backport #21921)
…de and rider (backport #21921)"
…lease/stable/6.4/pr-21921 fix: Fix cannot HR app with project dependency with code and rider (backport #21921)"
closes #21893
closes #21549
closes #20820
🐞 Bugfix
Cannot HR app with proejct depedency with code and rider
What is the current behavior? 🤔
App's TFM if forcefully pushed to all projects, including referenced project that might not have the same one
What is the new behavior? 🚀
App's TFM is applied only on the head project
PR Checklist ✅
Screenshots Compare Test Runresults.