development.md

Development and tests

Home · English guides · Русские руководства

Develop on Windows 10/11 x64 with VS Code and uv. Visual Studio is not required. Dependencies are downloaded into the checkout; the pinned Go SDK builds the HTTP/3 diagnostic helper and the two network core DLLs. The DLL build also downloads a checksum-pinned Zig C compiler; Go is not needed on users' computers. The same compiler builds the small C launcher for personal installations; this launcher needs no .NET runtime and starts only the current user's MegaProxy scheduled task. See native core architecture and trust checks.

setup.cmd
build.cmd
run.cmd

Approve UAC when requested. DEV has separate processes, icons, settings and startup entries. Manual mode runs directly from the build output; sign-in/service modes use the isolated DEV installation. build.cmd --dev builds without launching.

stop-prod.cmd stops the production channel. cleanup-dev.cmd (also uninstall-dev.cmd) removes DEV services, startup entries and installed binaries while preserving settings. install.cmd --mode manual|login|service selects a mode explicitly.

Command	Checks
tools-test.cmd	Python build/release tools
build-core.cmd --dev	Build Stable and Experimental DLLs and the isolated DEV host
test-core.cmd --signed	Native lifecycle, local forwarding and mutual signature checks
test.cmd	Configuration and core validation
ui-test.cmd	UI, service and lifecycle fixtures
h3-test.cmd	Local HTTP/3, HTTPS Jump and fallback
ssh-test.cmd	Local SSH authentication and Jump
ipv6-test.cmd	IPv6 routing across all proxy types using local real cores
run-trace-probe.cmd	Interactive Cloudflare trace and 50 MB speed measurements

The IPv6 suite uses local SOCKS ingress instead of TUN and does not test external IPv6 connectivity or Wintun. Logs and test reports remain under artifacts. test-core.cmd --signed --tun additionally creates and closes a test Wintun adapter without automatic routes; it requires administrator rights. CI runs this check. For release signing, packaging, CI gates and retries, see Installer and release automation.

The CI native-core core_smoke.py --tun checks also exercise strict routing with IPv6 blocked, disabled with loopback compatibility, and enabled, using both DLLs. They verify IPv4/IPv6 TCP loopback and that the IPv6 block disappears after core shutdown. Routes are restricted to documentation subnets, but WFP and DNS filters are system-wide while the test runs: use a disposable Windows runner with admin rights, not a workstation with an active VPN. A failed baseline loopback check is an error, not a skip. The configuration suite covers all 24 combinations of route mode, profile/system permissions and the blocking option, including DNS policy.

Release assets after 0.6.0 contain the installer, the complete application ZIP, the source ZIP and verification metadata. Both native cores are already in the application ZIP and installer; no separate core ZIPs are published. The signed manifest retains sing-box and sing-box-h3 component inventories for older reboot-update workers, referencing the same application ZIP. Release retries and changelog baseline selection still recognize the old asset layout through 0.6.0.