2dog.browser-wasm.release
4.7.2.11
dotnet add package 2dog.browser-wasm.release --version 4.7.2.11
NuGet\Install-Package 2dog.browser-wasm.release -Version 4.7.2.11
<PackageReference Include="2dog.browser-wasm.release" Version="4.7.2.11" />
<PackageVersion Include="2dog.browser-wasm.release" Version="4.7.2.11" />
<PackageReference Include="2dog.browser-wasm.release" />
paket add 2dog.browser-wasm.release --version 4.7.2.11
#r "nuget: 2dog.browser-wasm.release, 4.7.2.11"
#:package 2dog.browser-wasm.release@4.7.2.11
#addin nuget:?package=2dog.browser-wasm.release&version=4.7.2.11
#tool nuget:?package=2dog.browser-wasm.release&version=4.7.2.11
2dog.browser-wasm
Browser (WebAssembly) support for 2dog: statically links the
Godot engine into your .NET browser-wasm publish and ships the Godot web boot
shell. Your C# code hosts Godot in the browser – the same inversion 2dog does on
desktop.
How it works
The .NET browser-wasm runtime is the Emscripten main module. During
dotnet publish -r browser-wasm, the wasm-tools workload relinks
dotnet.native.wasm with Godot's static archive (libgodot.a) and JS glue from
this package. Game content is exported to a .pck on your build machine (via
the desktop editor packages 2dog already depends on) and served next to the app
bundle.
Requirements
- .NET SDK 10.0+ with the
wasm-toolsworkload (dotnet workload install wasm-tools) - A host project:
net10.0,OutputType=Exe,RuntimeIdentifier=browser-wasm,PackageReferenceto2dogand2dog.browser-wasm,<GodotProjectDir>set - The Godot project needs a
Webexport preset, a solution file, andTWODOG_WEB_BOOT+AllowUnsafeBlocksin its csproj - A
wwwroot/index.htmlboot page (create a project withdnx 2dog new MyGame --webfor a working setup out of the box) - Or a Blazor WebAssembly project: the package detects the Blazor SDK and
leaves layout and boot to Blazor;
2dog.blazor'sGodotViewstarts the engine (dnx 2dog new MyGame --blazor)
Usage
dotnet publish
(The 2dog web host template defaults the configuration to Release; pass
-c Debug for an unoptimized build.)
Serve the generated AppBundle/ directory with any static file server. The
single-threaded engine build requires no COOP/COEP headers.
Configuration and limitations
See the Browser Host documentation for the full property reference, loading-performance guidance, deployment behavior, and current browser limitations.
Learn more about Target Frameworks and .NET Standard.
This package has no dependencies.
NuGet packages (1)
Showing the top 1 NuGet packages that depend on 2dog.browser-wasm.release:
| Package | Downloads |
|---|---|
|
2dog.browser-wasm
Browser (wasm) meta package for twodog. Statically links the Godot engine into your .NET browser-wasm publish and ships the Godot web boot shell. Reference this package alongside twodog (2dog) in a net10.0+ browser-wasm host project. Requires the wasm-tools workload. |
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 4.7.2.11 | 78 | 9/28/2026 |
| 4.7.2.9 | 75 | 9/28/2026 |
| 4.7.2.7 | 74 | 9/27/2026 |
| 4.7.2.6 | 187 | 9/24/2026 |
| 4.7.2.5 | 86 | 9/23/2026 |
| 4.7.2.4 | 207 | 9/6/2026 |
| 4.7.2.3 | 196 | 9/3/2026 |
| 4.7.2.2 | 209 | 8/27/2026 |
| 4.7.2.1 | 176 | 8/26/2026 |
| 4.7.2 | 170 | 8/26/2026 |
| 4.7.1.39 | 236 | 8/16/2026 |
| 4.7.1.38 | 276 | 8/14/2026 |