Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Static web assets][Fixes #AspNetCore/17079] PublishSingleFile results in 404 errors for Nuget components #1415

Merged
merged 1 commit into from
Jan 15, 2020

Conversation

javiercn
Copy link
Member

@javiercn javiercn commented Dec 5, 2019

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.

Copy link
Contributor

@pranavkm pranavkm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is particularly low risk because we already do this by default for all Content files in the wwwroot directory: https://github.com/aspnet/AspNetCore-Tooling/blob/master/src/Razor/src/Microsoft.NET.Sdk.Razor/Sdk/Sdk.Razor.StaticAssets.ProjectSystem.props#L30. These are effectively the same category of files, we just missed these along with the others.

@jamshedd jamshedd modified the milestones: 3.1.x, 3.1.1 Dec 10, 2019
@jamshedd
Copy link
Member

Approved for 3.1.1

@mkArtakMSFT mkArtakMSFT modified the milestones: 3.1.1, 3.1.2 Dec 11, 2019
@mkArtakMSFT
Copy link
Member

These were approved for 3.1.2, so updating the milestone accordingly /cc @jamshedd

@vivmishra
Copy link

Moved to Mar as per Tactics. Will need to be explicitly approved for Feb, if required.

@vivmishra vivmishra modified the milestones: 3.1.2, 3.1.3 Jan 9, 2020
@mkArtakMSFT
Copy link
Member

Moving this back to 3.1.2 (Feb) per later decision from Tactics (@jamshedd , @vivmishra)

@mkArtakMSFT mkArtakMSFT modified the milestones: 3.1.3, 3.1.2 Jan 15, 2020
@mkArtakMSFT mkArtakMSFT merged commit 02de339 into release/3.1 Jan 15, 2020
@mkArtakMSFT mkArtakMSFT deleted the javiercn/swa-single-file-publish-fix branch January 15, 2020 02:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants