Skip to content

DivineLabs Installer 0.2.0 Preview — superseded by 0.2.1

Pre-release
Pre-release

Choose a tag to compare

View all tags
@Ps1xo-On1kS Ps1xo-On1kS released this 18 Oct 16:44
v0.2.0
bb3ba23

Superseded by 0.2.1, which fixes omitted configuration defaults and legacy metadata reading. Download 0.2.1 for new integrations.

Known issue: 0.2.0 can lose defaults for omitted JSON configuration fields, including template identity. Use fully specified configuration files, or upgrade to 0.2.1 once published. Existing artifacts are preserved unchanged.

DivineLabs Installer 0.2.0 Preview

One installation engine, reusable UI components and ready-made templates.

Choose your integration

  • Core: UI-independent IInstallerEngine API, typed install/uninstall requests, async work, progress, cancellation, receipt inspection and recovery. InstallAsync also updates existing installations.
  • Platforms: optional Windows/macOS/Linux registration, shortcuts and installation discovery.
  • Components: bindable Avalonia StepIndicator, DirectoryPicker and OperationProgressView, independent of Core, Platforms and Classic.
  • Templates.Classic: the current DivineLabs design as a reusable ClassicWindow/ClassicSession library. Styles and resources stay scoped to its window.
  • Config SDK: the same divinepack workflow and native standalone installer, now consuming those libraries and public API.

The four .nupkg files below are .NET 10 libraries for a local NuGet feed, including XML API documentation. They are not published to nuget.org in this preview. Native SDK archives support config-only packaging without a .NET toolchain on the application developer's machine.

Start here

Compatibility

Classic is the default template. Config-only integration remains supported. The new builder requires runtime format 2 with explicit template identity, and rejects incompatible old runtimes before output. Use a 0.2 target SDK for cross-packaging.

The engine reads 0.1 packages/configs/receipts. Newly written metadata includes template identity; old strict readers cannot read it. Keep the new maintenance runtime when updating standalone installations. Downgrading readers or changing maintenance ownership requires an explicit migration.

Embedded hosts own license acceptance, package trust, update policy and uninstall UX. The examples disable OS integrations unless a matching standalone runtime is supplied. The in-process API is .NET 10; other languages can use the native CLI.

Verification

All six native SDKs passed contract checks, Native AOT compilation, config-driven bundle construction, silent installation and installed-uninstaller/data-retention smoke checks. Both independent hosts compiled through local-feed NuGet packages. All 36 Classic frames rendered in both languages/themes with a host-resource isolation assertion; the custom launcher also rendered. A package-based launcher was additionally published as a Windows x64 Native AOT executable locally.

Release artifacts are from source commit bb3ba23. Checks cover SDK file hashes, native binary headers, runtime format/template/version, source commit, debug-artifact exclusion and NuGet dependency boundaries/source metadata/API XML. See SHA256SUMS.txt and validation.json.

Preview scope

Extract generated installer archives before launch. OS/native graphics dependencies remain. Single-file self-extracting delivery, MSI/PKG/DEB/RPM, signing/notarization, automatic update feeds and symlink payloads remain outside this preview. Existing transaction/recovery guarantees are preserved; arbitrary-application or production acceptance is not claimed. MIT; preserve bundled third-party notices.

Assets 14
Loading