2dog.browser-wasm.double
4.8.0.195
dotnet add package 2dog.browser-wasm.double --version 4.8.0.195
NuGet\Install-Package 2dog.browser-wasm.double -Version 4.8.0.195
<PackageReference Include="2dog.browser-wasm.double" Version="4.8.0.195" />
<PackageVersion Include="2dog.browser-wasm.double" Version="4.8.0.195" />
<PackageReference Include="2dog.browser-wasm.double" />
paket add 2dog.browser-wasm.double --version 4.8.0.195
#r "nuget: 2dog.browser-wasm.double, 4.8.0.195"
#:package 2dog.browser-wasm.double@4.8.0.195
#addin nuget:?package=2dog.browser-wasm.double&version=4.8.0.195
#tool nuget:?package=2dog.browser-wasm.double&version=4.8.0.195
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, and a2dog.godotsharpreference andAllowUnsafeBlocksin 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.
-
.NETStandard 2.0
- 2dog.browser-wasm.debug.double (= 4.8.0.195)
- 2dog.browser-wasm.release.double (= 4.8.0.195)
GitHub repositories
This package is not used by any popular GitHub repositories.
| Version | Downloads | Last Updated |
|---|---|---|
| 4.8.0.195 | 0 | 11/13/2026 |
| 4.8.0.193 | 0 | 11/13/2026 |
| 4.8.0.190 | 0 | 11/13/2026 |
| 4.8.0.188 | 0 | 11/13/2026 |
| 4.8.0.176 | 0 | 11/12/2026 |
| 4.8.0.163 | 0 | 11/12/2026 |
| 4.8.0.160 | 1 | 11/10/2026 |
| 4.7.2.197 | 0 | 11/13/2026 |
| 4.7.2.192 | 0 | 11/13/2026 |
| 4.7.2.175 | 0 | 11/12/2026 |
| 4.7.2.162 | 8 | 11/10/2026 |
| 4.7.2.159 | 0 | 11/10/2026 |
| 4.7.2.158 | 0 | 11/9/2026 |
| 4.7.2.154 | 0 | 11/8/2026 |