-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Add WebAssemblyHotReloadCapabilities msbuild property #59094
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
base: release/9.0
Are you sure you want to change the base?
Conversation
Enables Hot Reload to detect capabilities before WASM runtime is loaded into the browser.
@MackinnonBuck @javiercn ptal |
@tmat can you ask tactics for approval on this one? |
Is this still needed? |
Yes, although it's currently unclear which branch it should go to. |
@tmat is this needed in the 9.0 release? |
We can move it to main. |
@@ -2,6 +2,7 @@ | |||
<PropertyGroup> | |||
<BlazorWebAssemblyJSPath>$(MSBuildThisFileDirectory)blazor.webassembly.js</BlazorWebAssemblyJSPath> | |||
<BlazorRoutingEnableRegexConstraint Condition="'$(BlazorRoutingEnableRegexConstraint)' == ''">false</BlazorRoutingEnableRegexConstraint> | |||
<WebAssemblyHotReloadCapabilities>Baseline;AddMethodToExistingType;AddStaticFieldToExistingType;NewTypeDefinition;ChangeCustomAttributes;AddInstanceFieldToExistingType;GenericAddMethodToExistingType;GenericUpdateMethod;UpdateParameters;GenericAddFieldToExistingType</WebAssemblyHotReloadCapabilities> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this go to the underlaying WebAssembly SDK? It's common to all ".NET in browser", not specific to Blazor, right?
Enables Hot Reload to detect capabilities before WASM runtime is loaded into the browser.
Contributes to a fix of #59027