Description
I encountered a build failure when attempting to build a project created with the wasmconsole template using the .NET 11 SDK.
While this template worked in previous versions, it currently fails to compile or link correctly in the .NET 11 environment.
Reproduction Steps
- dotnet workload add wasm-tools wasm-experimental
- dotnet new wasmconsole --framework net11.0
- dotnet build
Expected behavior
The wasmconsole project should build and run successfully on .NET 11, maintaining parity with previous .NET versions.
Alternatively, if the wasmconsole template is intentionally being deprecated or replaced by another mechanism in .NET 11, the template should be officially dropped/removed from the SDK to prevent user confusion.
Actual behavior
$ LANG=en-US dotnet build
/Users/yamachu/Projects/github.com/yamachu/tmp/wasmconsole/wasmconsole.csproj : error NU1102:
Unable to find package Microsoft.NETCore.App.Runtime.browser-wasm with version (= 11.0.0-preview.3.26207.10
6)
- Found 27 version(s) in nuget.org [ Nearest version: 6.0.0-preview.3.21201.4 ]
- Found 0 version(s) in local
- Found 0 version(s) in /usr/local/share/dotnet/library-packs
- Found 0 version(s) in net10-nightly
- Found 0 version(s) in maui-nightly
Regression?
No response
Known Workarounds
Run: dotnet new wasmconsole --framework net10.0
or dotnet new wasmbrowser
Configuration
- dotnet --version
- 11.0.100-preview.3.26207.106
Other information
ref?: #102743
Description
I encountered a build failure when attempting to build a project created with the
wasmconsoletemplate using the .NET 11 SDK.While this template worked in previous versions, it currently fails to compile or link correctly in the .NET 11 environment.
Reproduction Steps
Expected behavior
The wasmconsole project should build and run successfully on .NET 11, maintaining parity with previous .NET versions.
Alternatively, if the wasmconsole template is intentionally being deprecated or replaced by another mechanism in .NET 11, the template should be officially dropped/removed from the SDK to prevent user confusion.
Actual behavior
Regression?
No response
Known Workarounds
Run:
dotnet new wasmconsole --framework net10.0or
dotnet new wasmbrowserConfiguration
Other information
ref?: #102743