-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Set some new Wasm properties so the Sdk can use Workloads when available #32036
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
Conversation
What is going on with CI in this PR? |
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
@lewing Looks like this PR happened during a period when CI was behaving badly. I've asked it to restart the CI run. @pranavkm You're the main expert about this on the Blazor side, so can you approve if you're happy with it? From my point of view this looks fine and I would just approve it, but want to make sure you've had a chance to see it first. |
Rebased to get CI green, cc @pranavkm |
@danroth27 thoughts on the description? |
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.
Description is fine by me. FYI @danroth27 for input
Merging to keep things moving, but we can tweak the description further later if @danroth27 has feedback. |
sdk part in dotnet/sdk#17092
This doesn't change any behavior without the sdk change but, with the sdk change it allows the Browser build to enable runtime relink/build outside of RunAOTCompilation during publish. Enabling additional features and/or size reductions in a published app.