Centralize common package properties and clean project layout #73
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
We also move towards a centralized release cycle by having all projects synched to the same version.
This will ensure any pack issues are correctly reported. NU5128 can be avoided on template packages by setting the SuppressDependenciesWhenPacking property.
We also move the icon asset to the build folder and avoid duplication of asset file names in package project properties.
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.
In preparation for the new release, we centralize package properties, unify package versioning to use Source Link and support a single release cycle for both generator and template packages, remove unused files, and generally clean the project layout to remove redundant attributes.