2dog 4.7.2.127

2dog

The .NET Tool for 2dog, which runs Godot as a library from your own .NET entry point. Point it at a Godot project and it adds .NET hosts: desktop, web, WebXR, Avalonia, Blazor, WinForms, WinUI 3, MAUI, Android, a C# REPL, and xUnit, NUnit or gdUnit tests. Then it keeps them healthy with 2dog doctor and current with 2dog update.

The dotnet new templates ship separately as 2dog.templates. To reference the engine from your own code, use 2dog.engine instead.

Getting started

With the .NET 10 SDK, run it without installing:

cd path/to/MyGame        # the folder with project.godot
dnx 2dog add             # pick hosts interactively
dotnet run --project MyGame.2dog

Or start from scratch with dnx 2dog new MyGame. Every prompt has a flag, so this runs unattended:

dnx 2dog add --web --xunit --yes

Other ways in: dotnet tool install -g 2dog installs the 2dog command, and dotnet new install 2dog.templates && dotnet new 2dog -n MyGame uses the template.

Your Godot project stays where it is. Each host is a nested folder with a .gdignore, added to the solution beside your game:

MyGame/
  project.godot
  MyGame.csproj      <- created or minimally patched
  MyGame.slnx        <- created, or an existing .sln is migrated (backup kept)
  MyGame.2dog/       <- desktop host
  MyGame.web/        <- browser host
  MyGame.xunit/      <- tests

The tool never moves, renames or deletes your files, except for the announced .sln migration and --rename. Run it again to add more hosts; existing ones are left alone. The guide and CLI reference cover the details.

Commands

Options

Exit codes: 0 ok, 1 usage error, 2 tool error (including a failed restore, which keeps the created files), 3 doctor findings remain or a repl exec submission failed, 124 repl exec timed out, 130 cancelled. Nothing prompts in a pipe or in CI. Workloads, troubleshooting and every verb in depth: 2dog.dev/dnx-2dog.