[wasm] Delete obsolete wasm console templates and related WASI build tests

docs/workflow/wasm-documentation.md

@@ -97,7 +97,7 @@ See the [Building for WebAssembly](#building-for-webassembly) section above for
 
 ### How do I test Wasm changes end to end?
 
-Use Wasm.Build.Tests or Wasi.Build.Tests. See the [Wasm.Build.Tests README](../../src/mono/wasm/Wasm.Build.Tests/README.md) for detailed instructions.
+Use Wasm.Build.Tests for browser scenarios. For WASI scenarios, validate against a sample app under `src/mono/sample/wasi`.
 
 ### How do I enable multi-threading?
 

eng/pipelines/common/evaluate-default-paths.yml

@@ -268,7 +268,6 @@ jobs:
  - src/mono/wasi/build/*
  - src/mono/wasi/runtime/*
  - src/mono/wasi/testassets/*
- - src/mono/wasi/Wasi.Build.Tests/*
  - ${{ parameters._const_paths._wasm_chrome }}
  - ${{ parameters._const_paths._wasm_src_native }}
  - src/tasks/*
@@ -312,7 +311,7 @@ jobs:
  - ${{ parameters._const_paths._always_exclude }}
  - ${{ parameters._const_paths._perf_pipeline_specific_only }}
 
- # Wasm except Wasm.build.Tests, Wasi.build.Tests and debugger
+ # Wasm-specific paths excluding Wasm.Build.Tests, WASI (build/runtime/testassets), and the debugger
  - subset: wasm_specific_except_wbt_dbg
  combined: true
  include:
@@ -337,7 +336,6 @@ jobs:
  - src/mono/wasi/build/*
  - src/mono/wasi/runtime/*
  - src/mono/wasi/testassets/*
- - src/mono/wasi/Wasi.Build.Tests/*
  - src/mono/nuget/Microsoft.NET.Runtime*
  - src/mono/nuget/Microsoft.NET.Workload*
  - src/mono/nuget/Microsoft.NETCore.BrowserDebugHost.Transport/*

eng/testing/scenarios/BuildWasiAppsJobsList.txt

@@ -1 +0,0 @@
-Wasi.Build.Tests.BuildPublishTests

src/libraries/tests.proj

@@ -696,12 +696,6 @@
  ('$(ContinuousIntegrationBuild)' != 'true' and '$(TestAssemblies)' == 'true'))"
  BuildInParallel="false" />
 
- <ProjectReference Include="$(WasiProjectRoot)\Wasi.Build.Tests\*.Tests.csproj"
- Exclude="@(ProjectExclusions)"
- Condition="'$(TargetOS)' == 'wasi' and
- (('$(ContinuousIntegrationBuild)' == 'true' and '$(TestWasmBuildTests)' == 'true') or
- ('$(ContinuousIntegrationBuild)' != 'true' and '$(TestAssemblies)' == 'true'))"
- BuildInParallel="false" />
  </ItemGroup>
 
  <ItemGroup Condition="'$(ArchiveTests)' == 'true' and '$(TargetOS)' == 'ios' and '$(RunAOTCompilation)' == 'true'">

src/mono/browser/README.md

@@ -189,22 +189,11 @@ Also check [bench](../sample/wasm/browser-bench/README.md) sample to measure mon
 
 ## Templates
 
-The wasm templates, located in the `templates` directory, are templates for `dotnet new`, VS and VS for Mac. They are packaged and distributed as part of the `wasm-experimental` workload. We have 2 templates, `wasmbrowser` and `wasmconsole`, for browser and console WebAssembly applications.
+The wasm templates, located in the `templates` directory, are templates for `dotnet new`, VS and VS for Mac. They are packaged and distributed as part of the `wasm-experimental` workload. The remaining template is `wasmbrowser` for browser WebAssembly applications.
 
 For details about using `dotnet new` see the dotnet tool [documentation](https://learn.microsoft.com/dotnet/core/tools/dotnet-new).
 
-To test changes in the templates, use `dotnet new install --force src/mono/wasm/templates/templates/browser`.
-
-Example use of the `wasmconsole` template:
-
-```console
-> dotnet new wasmconsole
-> dotnet publish
-> cd bin/Debug/net9.0/browser-wasm/AppBundle
-> node main.mjs
-Hello World!
-Args:
-```
+To test changes in the template, use `dotnet new install --force src/mono/wasm/templates/templates/browser`.
 
 ## ES6 modules
 

src/mono/nuget/Microsoft.NET.Runtime.WebAssembly.Wasi.Sdk/Microsoft.NET.Runtime.WebAssembly.Wasi.Sdk.pkgproj

@@ -21,7 +21,7 @@
  <PackageFile Include="$(WasmProjectRoot)build\WasmApp.Common.props" TargetPath="Sdk" />
  <PackageFile Include="$(WasmProjectRoot)build\WasmApp.Common.targets" TargetPath="Sdk" />
 
- <PackageFile Include="$(WasiProjectRoot)build\wasiconsole.runtimeconfig.template.json" TargetPath="Sdk" />
+ <PackageFile Include="$(WasiProjectRoot)build\wasi.runtimeconfig.template.json" TargetPath="Sdk" />
  </ItemGroup>
 
  <Target Name="_PrepareForPack" BeforeTargets="GetPackageFiles">

src/mono/wasi/Makefile

@@ -63,21 +63,6 @@ clean:
 run-tests-%:
 	$(DOTNET) build $(TOP)/src/libraries/$*/tests/ /t:Test $(_MSBUILD_WASM_BUILD_ARGS) $(MSBUILD_ARGS)
 
-run-build-tests:
-	$(DOTNET) build $(TOP)/src/mono/wasi//Wasi.Build.Tests/ /t:Test /bl $(_MSBUILD_WASM_BUILD_ARGS) $(MSBUILD_ARGS)
-
-submit-wbt-helix:
-	PATH="$(JSVU):$(PATH)" \
- $(DOTNET) build $(TOP)/src/mono/wasi/Wasi.Build.Tests/ /v:m /p:ArchiveTests=true /t:ArchiveTests $(_MSBUILD_WASM_BUILD_ARGS) $(MSBUILD_ARGS) && \
- BUILD_REASON=wasm-test SYSTEM_TEAMPROJECT=public BUILD_REPOSITORY_NAME=dotnet/runtime BUILD_SOURCEBRANCH=main \
- $(TOP)/eng/common/msbuild.sh --ci -restore $(TOP)/src/libraries/sendtohelix.proj \
- /p:TestRunNamePrefixSuffix=WasiBuildTests /p:HelixBuild=`date "+%Y%m%d.%H%M"` /p:Creator=`whoami` \
- /bl:$(TOP)/artifacts/log/$(CONFIG)/SendToHelix.binlog -v:m -p:HelixTargetQueue=$(HELIX_TARGET_QUEUE) \
- /p:RuntimeFlavor=mono /p:TargetRuntimeIdentifier= /p:MonoForceInterpreter= /p:TestScope=innerloop \
- /p:_Scenarios=buildwasmapps \
- $(_MSBUILD_WASM_BUILD_ARGS) \
- $(MSBUILD_ARGS)
-
 submit-tests-helix:
 	echo "\n** This will submit all the available test zip files to helix **\n"
 	BUILD_REASON=wasm-test SYSTEM_TEAMPROJECT=public BUILD_REPOSITORY_NAME=dotnet/runtime BUILD_SOURCEBRANCH=main \

src/mono/wasi/README.md

@@ -12,14 +12,8 @@ Here is a quick overview of how to consume published artifacts. Assuming .NET SD
 dotnet workload install wasi-experimental
 ```
 
-This will install workload for building .NET based WASI apps + basic template.
-Now you can create a new .NET application that targets WASI
-
-```
-dotnet new wasiconsole
-```
-
-And run it with
+This will install the workload for building .NET based WASI apps.
+You can start from the sample projects under `src/mono/sample/wasi`, or author a project that targets `wasi-wasm`, and run it with
 
 ```
 dotnet run