-
Notifications
You must be signed in to change notification settings - Fork 25.1k
Closed
Labels
BlazorPri1Source - Docs.msDocs Customer feedback via GitHub IssueDocs Customer feedback via GitHub Issueaspnet-core/svcblazor/subsvcdoc-enhancement
Description
Description
Consider adding a note about .NET WebAssembly build tools compatibility and installation instructions for .NET 8 projects.
From Marek ...
The table is about SDK version and TFM
- .NET 10 SDK
- targeting .NET 10 requires wasm-tools
- targeting .NET 9 requires wasm-tools-net9
- targeting .NET 8 requires wasm-tools-net8
- .NET 9 SDK
- targeting .NET 9 requires wasm-tools
- targeting .NET 8 requires wasm-tools-net8
- .NET 8 SDK
- targeting .NET 8 requires wasm-tools
The workload always installs into the SDK. If you install wasm-tools workload into .NET 9 SDK, the .NET 10 SDK won't have it. You'll need to install it again. Although multiple rows contain wasm-tools-net8 workload, it fact it is always a slightly different workload for the particular .NET SDK.
If you install the workload using checkbox in Visual Studio setup, the VS installer know about the workload and when it installs newer .NET SDK, it will install the workload automatically.
Page URL
Content source URL
Document ID
bbbdf15e-1918-cee9-ff03-0ebbca80e86e
Platform Id
0a8e8b8e-2e88-684e-022e-56238545d038
Article author
Metadata
- ID: bbbdf15e-1918-cee9-ff03-0ebbca80e86e
- PlatformId: 0a8e8b8e-2e88-684e-022e-56238545d038
- Service: aspnet-core
- Sub-service: blazor
Metadata
Metadata
Assignees
Labels
BlazorPri1Source - Docs.msDocs Customer feedback via GitHub IssueDocs Customer feedback via GitHub Issueaspnet-core/svcblazor/subsvcdoc-enhancement
Type
Projects
Status
Done