Remove Tizen workload; use the Tizen SDK package directly instead #17550
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
MrJul
added
enhancement
area-infrastructure
kekekeks
approved these changes
Nov 18, 2024
|
You can test this PR using the following package version. |
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.
What does the pull request do?
This PR removes the Tizen workload from the solution.
Not a week goes by without the solution being broken locally for one of the team's member.
Any local .NET SDK update always causes issues with the Tizen workload failing to restore properly, even if it's not related to the
workloads being updated. Workloads are terrible.
Instead, this PR directly references the Tizen SDK nuget package matching our current .NET SDK version.
The .NET SDK in global.json has also been updated to the latest 8.0.404.