Document guidelines for porting new packages #1206
Merged
Conversation
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
mthalman
approved these changes
Mar 20, 2025
ViktorHofer
reviewed
Mar 20, 2025
| @@ -84,6 +84,11 @@ generated packages show changes when being regenerated. | |||
|
|
|||
| You can search for known issues in the [Known Generator Issues Markdown file](docs/known_generator_issues.md). | |||
|
|
|||
| **Note:** When porting new packages between branches, you must regenerate the packages when crossing the 10.0/9.0 boundary. | |||
| This is because in 10.0 the generated projects switched from using PackageReference to PojectReference. | |||
There was a problem hiding this comment.
PojectReference -> ProjectReference
Merged
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 is something that was brought to attention in #1205 (comment)