Skip to content

Conversation

@MichalStrehovsky
Copy link
Member

Control over this is moving from dotnet/runtime repo build time to publish time so we need to set a default that matches the old build-time setting.

Ref dotnet/runtime#117012
Ref #49564

Control over this is moving from dotnet/runtime repo build time to publish time so we need to set a default that matches the old build-time setting.

Ref dotnet/runtime#117012
Ref #49564
Copilot AI review requested due to automatic review settings June 27, 2025 09:53
@MichalStrehovsky MichalStrehovsky requested a review from a team as a code owner June 27, 2025 09:53
@github-actions github-actions bot added the Area-AspNetCore RazorSDK, BlazorWebAssemblySDK, dotnet-watch label Jun 27, 2025
@dotnet-policy-service
Copy link
Contributor

Thanks for your PR, @@MichalStrehovsky.
To learn about the PR process and branching schedule of this repo, please take a look at the SDK PR Guide.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

Sets the default value of the Http3Support feature switch to false in the Blazor WebAssembly 6.0 SDK targets so that publish-time behavior matches the previous build-time default.

  • Adds a new <Http3Support> property with a fallback of false.

<UseSystemResourceKeys Condition="'$(UseSystemResourceKeys)' == ''">true</UseSystemResourceKeys>
<UseSizeOptimizedLinq Condition="'$(UseSizeOptimizedLinq)' == ''">true</UseSizeOptimizedLinq>
<EnableUnsafeUTF7Encoding Condition="'$(EnableUnsafeUTF7Encoding)' == ''">false</EnableUnsafeUTF7Encoding>
<Http3Support Condition="'$(Http3Support)' == ''">false</Http3Support>
Copy link

Copilot AI Jun 27, 2025

Choose a reason for hiding this comment

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

This change introduces a new default for Http3Support. Consider adding or updating an automated test in the SDK targets tests to verify that when Http3Support is unset it indeed defaults to false.

Copilot generated this review using guidance from repository custom instructions.
Copy link
Member

Choose a reason for hiding this comment

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

Should this be on the wasm SDK directly? /cc @maraf

Ideally, we want this for all webassembly apps, not just Blazor ones

Copy link
Member

@pavelsavara pavelsavara Jun 27, 2025

Choose a reason for hiding this comment

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

We don't have same underlying SocketsHttpHandler in wasm. We use browser's fetch. So this should have no impact.

Copy link
Member Author

Choose a reason for hiding this comment

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

Should this be on the wasm SDK directly? /cc @maraf

I'm putting this on the other WASM related file here: #49583 (I had that PR out as dotnet/runtime#117081 originally, that's why it's a separate PR).

These both duplicate a lot of these properties and I don't know what's the difference so I'm just piling on where related things are already set.

@MichalStrehovsky MichalStrehovsky merged commit 852aab1 into main Jun 27, 2025
27 checks passed
@MichalStrehovsky MichalStrehovsky deleted the MichalStrehovsky-patch-1 branch June 27, 2025 22:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area-AspNetCore RazorSDK, BlazorWebAssemblySDK, dotnet-watch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants