Add net8.0 target for TranslationLayer#15375
Merged
nohwnd merged 1 commit intomicrosoft:mainfrom Feb 10, 2026
Merged
Conversation
This was referenced Apr 22, 2026
Merged
Open
Open
This was referenced Apr 22, 2026
Open
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Translation layer targets netstandard2.0 but depends on object model that has net8.0 target, which will restore net8.0 object model in consuming project if the project supports net8.0 or newer.
To avoid this mixup of dependencies, add target for the translation layer. Especially since we already support .NET Framework explicitly.
Remove dependency dlls that we already ship in object model package, and fix dependencies on newtonsoft and object model for netstandard2.0.