-
Notifications
You must be signed in to change notification settings - Fork 437
Create WASM installers for optional workloads #10685
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
| <ItemGroup> | ||
| <!-- Overrides for Visual Studio setup generation. If the workload definition IDs change, | ||
| these must be updated. --> | ||
| <ComponentResources Include="microsoft-net-sdk-blazorwebassembly-aot" Title=".NET WebAssembly Build Tools" |
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.
@danroth27 @lewing can you take a look at the title/description. This is what would show in VS setup UI
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.
Looks good to me.
|
We're likely going to be blocked on merging until dotnet/arcade#7420 is resolved and we take new Arcade update in Installer. |
| @@ -1,17 +1,25 @@ | |||
| { | |||
| "sdk": { | |||
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.
what is the SDK here?
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.
That allows Arcade to install the local SDK so that full framework msbuild can locate it. This was the recommendation from Arcade to help address the issue where a local SDK can't be located (together with the change in configure-toolset.ps1)
Add new build leg to create WASM installers for .NET optional workloads