Skip to content
Project referenceDevelopmentEngine ccf7d03f
Outdated
  • Verified Support Pack preparation, publication and protected consumption.

Verified Support Pack preparation, publication and protected consumption.

Start with distribution composition and Support Pack preparation.

Prepare and consume a Support Pack explains planning, cold work, valid reuse and the distinction from a final game. This neutral library owns the publisher/provisioning transaction without registering built-in platforms or referencing concrete backend tools/Editor.

The publisher freezes unique target sources. CreatePlanAsync validates source/template/SDK/host inputs without an output directory. After target/cancellation checks and a write lease, VerifyInputsAsync revalidates the complete request before preparation-index lookup. A validated complete match returns a protected publication; otherwise source-owned preparation fills staging, platform validation establishes a complete closure, and atomic current selection follows immutable publication.

Preparation identity combines recipe, selected binding configuration/inheritance, generator/extensions, actual managed graph, templates and platform validator. Artifact identity hashes the complete Pack file set. A published self-contained Pack does not depend on the continued presence of rebuildable workspaces. Lock-wait and pre-selection freshness remain mandatory.

PlayerSupportPackPublication uniquely owns reading protection and reports post-commit index/staging cleanup diagnostics separately. Hold it until all compilation/linking/copying finishes. The catalog’s PlayerSupportPackLease independently pins directory consumption. Failures before selection retain the old complete output.

SourcePlayerSupportPackProvisioner locates current source for authoring hosts; a distribution host may instead consume installed immutable Packs. A custom source supplies an immutable plan, a real input verifier and fully drained PrepareAsync. The plan does not retain ongoing cross-phase work.

PlayerSupportPackBuildContext.sdk and recorded CLI entry stay frozen; staging does not resolve another SDK through PATH/global.json. Managed compilation and PlayerLink extraction share one fixed source workspace. Frozen InnoShaderToolSourceRoot keeps offline Shader tools with their original protected owner instead of creating another cache in the copy. Native preparation results stay alive throughout the dependent managed build and staging.

Supply existing live dependencies. This example checks the host contract; it does not initialize a complete product or certify a physical device.

using System.Collections.Generic;
using Inno.Build.SupportPacks;
static PlayerSupportPackPublisher CreatePublisher(IEnumerable<IPlayerSupportPackSource> sources)
{
return new PlayerSupportPackPublisher(sources);
}

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

Browse types and members.

Project: Inno.Build.SupportPacks.Core
Source: build/support/Inno.Build.SupportPacks.Core/Inno.Build.SupportPacks.Core.csproj

Type API Description
FilePlayerSupportPackPreparation engine Prepares file-based product inputs using injected target tools, source locations and native closure.
IPlayerSupportPackSource engine Prepares one platform’s runtime and compiler inputs without owning installation or replacement.
PlayerSupportPackBuildContext engine Supplies preparation with explicit paths and a selected SDK, excluding installed output.
PlayerSupportPackClosureValidator engine Combines a platform’s layout checks with distribution-selected managed, binding and native requirements.
PlayerSupportPackFiles engine Prepares explicit product source and reference inputs for isolated Support Pack publication.
PlayerSupportPackPlan engine Holds validated, frozen preparation inputs without owning running processes or staging resources.
PlayerSupportPackPlanningContext engine Supplies read-only discovery inputs before a publication directory exists.
PlayerSupportPackPreparationIdentity engine Freezes a Support Pack’s source preparation identity independently of reconstructible build outputs.
PlayerSupportPackPublication engine Owns a successfully selected Pack and immutable diagnostics from work after its commit.
PlayerSupportPackPublisher engine Installs verified Support Packs with rollback protection using explicitly registered platform sources.
PlayerSupportPackRequirements engine Freezes distribution-selected files and native deployment groups independently of platform packaging.
SourcePlayerSupportPackProvisioner engine Prepares current checkout and SDK inputs and selects a verified, immutable Player Support Pack.