Skip to content
Project referenceDevelopmentEngine ccf7d03f

Explicit CoreCLR, Mono WebAssembly and NativeAOT deployment compilation for prepared engine products.

Read the linked task or ownership explanation before using the exact API below.

Select a compiler through product composition

Section titled “Select a compiler through product composition”

Publish a managed deployment explains strategy selection, SDK resolution, native closure validation, execution aliases, cancellation and diagnostic files. Platform contributions declare supported RIDs; a declared capability is not proof that this host has the required cross-compilation workload.

The library implements the neutral Managed compiler contract using Toolchains SDK/process services. Scene/content orchestration, final packaging, signing and UI remain outside it. Existing prepared-project examples belong to managed build contracts.

Compilers borrow the supplied tool host and workspace service, freeze supported identifiers and return a validated compilation result. Internal publishing request/executor classes are implementation details. The caller owns final staging/publication. Successful compilation still needs actual product execution and any applicable device or visual checks.

The source project defines the selected host declarations. Script projection and platform execution require their separate evidence.

Types and exact member contracts retain declarations and source XML from the recorded engine capture.