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 Compression Flag Breaking Change #283

Open
MackinnonBuck opened this issue Nov 7, 2023 · 0 comments
Open

Static Web Assets Compression Flag Breaking Change #283

MackinnonBuck opened this issue Nov 7, 2023 · 0 comments

Comments

@MackinnonBuck
Copy link
Member

This issue is a locked mirror of dotnet/aspnetcore#51922. See that issue for discussion.

Static Web Assets Compression Flag Breaking change

The <BlazorEnableCompression> flag was renamed to <CompressionEnabled> starting in the .NET 8 Preview 4 SDK.

Static web asset compression is still enabled by default when using the StaticWebAssets SDK. It can be disabled in the app's project file or from the .NET CLI:

MSBuild

<PropertyGroup>
  <CompressionEnabled>false</CompressionEnabled>
</PropertyGroup>

.NET CLI

dotnet publish -p:CompressionEnabled=false

Note that this change is associated with the version of the .NET SDK used to build the project and is independent of the project's TFM. For example, a project with a TargetFramework of net7.0 will need to react to this breaking change if it gets built with the .NET 8 SDK.

Context

The Static Web Assets feature was moved from the Blazor WebAssembly SDK into its own SDK in .NET 8. As part of this work, MSBuild properties with the name Blazor in them were renamed to indicate that they are not limited to Blazor scenarios.

@dotnet dotnet locked as resolved and limited conversation to collaborators Nov 7, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants