-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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
PublishSingleFile results in 404 errors for Nuget components #17079
Comments
@Webreaper thanks for contacting us. This can be a bug, we might not be adding ExcludeFromSingleFile to the static web assets. |
Updated to 8.4 build 2535 last night, and the problem is still present (I know you're still probably investigating so wasn't expecting it to be fixed :)) |
Any update on this? I've just updated to DotNetCore SDK v3.1.0 and the problem still happens. |
@Webreaper this is scheduled for preview5, so I wouldn't expect any action on this until the end of the year. You can probably workaround this through MSBuild extensibility by setting the ExcludeFromSingleFile property on the ResolvedFileToPublish items for the static web assets. |
Thanks for the update. I'm using normal publishing for now, but thanks for the tip! |
Removed the |
Developing a Blazor app in VS for Mac 8.4 Preview (8.4 build 2414) and publishing a single-file executable for Linux, the JS and CSS components for NuGet packages result in a 404 when executing the app. This worked fine when I did it about 2 weeks ago, so looks to be a regression in the latest preview version of 16.4 which installed within the last week.
To reproduce:
dotnet publish Damselfly.Web -r ubuntu.18.04-x64 -c Release /p:PublishSingleFile=true
ASP.Net Core version: I tried this with DotNet Core 3.1 preview, and just in case it was a regression with that version I also tried with DotNet Core 3.0. Same problem with both. So it looks like it's a regression with the single-file packaging for Blazor apps not including the _content folder properly.
Output of
dotnet --info
:The text was updated successfully, but these errors were encountered: