D Donkeh docs
GitHub

Using the deploy tab

Deploy builds the application targets into the project's builds folder, then serves that folder over the local network so a device or phone can download the result. The same server page accepts screenshots and writes them into the project's debug folder.

Build targets

The tab discovers the enabled hosts from the app project and lists them as build targets. The standard entries are:

TargetOutputResult
Desktopbuilds/desktopFramework-dependent desktop build.
Androidbuilds/androidSigned APK copied from the build output.
WebAssemblybuilds/wasmStatic site with index.html at the folder root.

Build All runs the targets in order. Each row also has its own build button. Builds run on a worker thread, so the app frame loop keeps running while dotnet works.

Output layout

MyApp/ ├── builds/ │ ├── desktop/ │ ├── android/ │ │ └── MyApp-Signed.apk │ └── wasm/ │ ├── index.html │ ├── dotnet.js │ └── _framework/ └── debug/ # screenshots uploaded from the Deploy server page

The default build configuration is Release. The deploy service exposes it as DevTools.Builds.Configuration; change it before starting a build. Custom targets can be added with DevTools.Builds.AddTarget(...).

Building

  1. Open the inspector and select Deploy.
  2. Choose a target row, or press Build All.
  3. Watch the per-target status and the shared build log at the bottom.
  4. Use the produced path to inspect the artifact locally, or start the download server.
Android signing The Android target builds an APK with the project's normal signing configuration. The signed APK is copied into builds/android with a device-friendly file name.

Starting the download server

The server turns the builds folder into a small browsable HTTP index. Toggle it with the download-server button in the Deploy tab. While it is running, the tab lists:

SettingDefaultNotes
Port8080Change while stopped; the server binds when started.
Root{project}/buildsSubfolders are browsable; files download directly.
BindingAll IPv4 interfacesWorks for localhost and LAN devices.
AuthNoneUse only on a trusted local network.

Uploading screenshots

Every page served by the download server also has an upload area. Drop screenshots onto it, or click it to browse, and each image is saved to {project}/debug. The application can then read those files as local context, for example to attach a visual regression screenshot to a bug report or an agent prompt.

Getting a build onto a device

Android

  1. Build the Android target.
  2. Start the download server.
  3. Open the server URL on the phone or tablet.
  4. Open android/ and download the signed APK.
  5. Install it from the browser or a file manager. The device may ask you to allow installs from the browser.

Desktop

Download the files from desktop/ to the target machine. The desktop output is framework-dependent, so the machine needs the matching .NET runtime.

WebAssembly

The site is under wasm/. Copy that folder to any static host that serves the right MIME types:

.js     text/javascript
.wasm   application/wasm
.json   application/json
.html   text/html
The download server is for downloads, not hosting the WASM app Its file server is intentionally minimal and does not provide the full MIME and compression behaviour a WebAssembly app expects. Use it to fetch builds/wasm, then serve the copied site with a proper static server.

Network checklist

Fast iteration Keep the Deploy tab open while iterating. Rebuild the target, refresh the browser listing, and download the new artifact; the output folder is reused between builds.