[Static web assets][Fixes #AspNetCore/17079] PublishSingleFile results in 404 errors for Nuget components #1415
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.
Description
Static web assets don't work properly with PublishSingleFile as they aren't excluded (like the rest of the web content is).
This fix simply adds a property and the tests necessary to make sure the assets are excluded when published.
Customer Impact
This blocks customers trying to publish ASP.NET Core apps as single files when the app uses static web assets.
The issue was customer reported dotnet/aspnetcore#17079
Regression?
No, but we broke this really close to 3.0 RTM and used to work before.
Risk
Low. It's a one line change and we've included a test that validates the fix.
Implementation details
Just adds the ExcludeFromSingleFile property to the resolved static web assets to publish.