Use props to hide files instead of .pp extension #26
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
The workaround of using the .pp extension no longer works in MSBuild 17. Using the `Visible` MSBuild property makes the intent more clear anyway. https://til.cazzulino.com/dotnet/nuget/hide-contentfiles-from-your-nuget-packages
|
That looks absolutely fantastic, many many thanks @gtbuchanan! |
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.
The workaround of using the .pp extension no longer works in MSBuild 17.2.1 when using
TargetFrameworks. Builds fail with an error like this:or this (depending on the situation):
Using the
VisibleMSBuild property makes the intent more clear anyway. The approach is adapted from here.Related to manuelroemer/IsExternalInit#14