如何将任意C#文件编译为独立的.wasm文件？——基于.NET 6 Blazor WebAssembly AOT编译场景

Great question! Let's start by clearing up your initial understanding: you're mostly correct—Blazor WebAssembly's AOT compilation does bundle the .NET runtime, your app code, and dependencies into that single dotnet.wasm file. But the good news is, you can compile individual C# files into standalone .wasm files without tying them to the full Blazor runtime. Here are two reliable methods:

1. Use the .NET WASI SDK (Experimental) #

The WebAssembly System Interface (WASI) lets .NET compile C# code into self-contained .wasm files that include only the necessary runtime bits (no full .NET runtime bundle). This is ideal for simple, console-style C# code that doesn't need Blazor's UI framework.

Step-by-Step: #

• First, install the WASI workload for .NET:

  dotnet workload install wasi-experimental
  

• Create a new console project (this works best for standalone WASM targets):

  dotnet new console -o StandaloneWasmDemo
  

• Open the project file (StandaloneWasmDemo.csproj) and modify it to target WASI:

  <Project Sdk="Microsoft.NET.Sdk">
    <PropertyGroup>
      <OutputType>Exe</OutputType>
      <TargetFramework>net8.0</TargetFramework>
      <RuntimeIdentifier>wasi-wasm</RuntimeIdentifier>
      <PublishTrimmed>true</PublishTrimmed> <!-- Reduces file size -->
    </PropertyGroup>
  </Project>
  

• Replace the default Program.cs with your custom C# code (e.g., a simple function or logic):

  using System;
  
  namespace StandaloneWasmDemo
  {
      class Program
      {
          static void Main(string[] args)
          {
              Console.WriteLine("Hello from standalone C# WASM!");
              int result = AddNumbers(5, 3);
              Console.WriteLine($"5 + 3 = {result}");
          }
  
          static int AddNumbers(int a, int b) => a + b;
      }
  }
  

• Publish the project to generate the standalone .wasm file:

  dotnet publish -c Release
  

• You'll find your standalone .wasm file at bin/Release/net8.0/wasi-wasm/publish/StandaloneWasmDemo.wasm. This file contains your compiled code plus only the minimal .NET runtime components needed to run it—no separate dotnet.wasm required.

2. Use Native AOT with WASM (For Optimized, Smaller Files) #

If you need even more control over file size and performance, use .NET's Native AOT feature with WASI. Native AOT compiles C# directly to WASM bytecode (no intermediate IL), resulting in smaller, faster-executing .wasm files.

Step-by-Step: #

• Follow the first two steps from the WASI method above (install workload, create project).
• Modify the project file to enable Native AOT:

  <Project Sdk="Microsoft.NET.Sdk">
    <PropertyGroup>
      <OutputType>Exe</OutputType>
      <TargetFramework>net8.0</TargetFramework>
      <RuntimeIdentifier>wasi-wasm</RuntimeIdentifier>
      <NativeAot>true</NativeAot> <!-- Enables direct WASM compilation -->
      <PublishTrimmed>true</PublishTrimmed>
    </PropertyGroup>
  </Project>
  

• Publish the project the same way:

  dotnet publish -c Release
  

• The resulting .wasm file will be significantly smaller than the WASI non-AOT version, as it skips IL interpretation entirely.

Key Notes #

• Feature Limitations: Not all C# features work with WASI/Native AOT. Reflection, dynamic code generation, and some runtime-dependent APIs may be restricted. Test your code thoroughly.
• Runtime Compatibility: Standalone WASM files compiled this way run in WASI-compatible environments (e.g., Node.js with @wasmer/wasi, Wasmtime runtime, or browsers using a WASI polyfill). They won't work directly in Blazor, since Blazor relies on its own dotnet.wasm runtime.

内容的提问来源于stack exchange，提问作者NextStep