Update tooling pointer, bump global.json to 8.0.403 #541
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Needs #540 for the TFM downgrade. |
Sergio0694
approved these changes
Oct 25, 2024
auto-merge was automatically disabled
October 31, 2024 18:38
Rebase failed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR:
maincommit.global.jsonto use version 8.0.403 instead of 8.0.201. This aligns with the version used by our tooling submodule, and enables implicit properties and project references when building with the Windows App SDK (see Cleanup of WindowsAppSDK implicit properties and project references Tooling-Windows-Submodule#221 (comment))Changes in tooling include:
[New]
wasdkMultiTarget can now setHasWinUItofalseto disable any UI-related dependencies under the TFMs used to target the Windows App SDK, aligning with the current behavior on UWP. See Conditionally reference WinAppSDK packages from HasWinUI prop Tooling-Windows-Submodule#217[Improvements]
wasdkMultiTarget is once again using19041instead of22621. SeeRevert WinAppSdkTargetFramework version from 22621 to 19041. Tooling-Windows-Submodule#220