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:
| Target | Output | Result |
|---|---|---|
| Desktop | builds/desktop | Framework-dependent desktop build. |
| Android | builds/android | Signed APK copied from the build output. |
| WebAssembly | builds/wasm | Static 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
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
- Open the inspector and select Deploy.
- Choose a target row, or press Build All.
- Watch the per-target status and the shared build log at the bottom.
- Use the produced path to inspect the artifact locally, or start the download server.
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:
- The loopback URL, for example
http://localhost:8080/. - One URL for each active IPv4 interface, so a phone on the same network can connect.
| Setting | Default | Notes |
|---|---|---|
| Port | 8080 | Change while stopped; the server binds when started. |
| Root | {project}/builds | Subfolders are browsable; files download directly. |
| Binding | All IPv4 interfaces | Works for localhost and LAN devices. |
| Auth | None | Use 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.
- The original file name is kept; a numeric suffix is added when the name already exists.
- Only image files are accepted, up to 32 MB each. Several files can be dropped at once.
- Uploads are written by the same local server, so the page must be opened from the server URL.
- The
debugfolder is ignored by Git in the framework repository.
Getting a build onto a device
Android
- Build the Android target.
- Start the download server.
- Open the server URL on the phone or tablet.
- Open
android/and download the signed APK. - 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
builds/wasm, then serve the copied site with a proper static
server.
Network checklist
- Phone and computer must be on the same network.
- Allow the application through the host firewall if the LAN URL is unreachable.
- If port 8080 is taken, stop the server, change the port, and start it again.
- The server has no authentication. Stop it when you are done.