Briosa Installer 0.4.0

Briosa Installer 0.4.0 is a security update. It rebuilds the self-contained Installer, CLI, launcher and Windows setup with .NET runtime 10.0.13 (SDK 10.0.402). That replaces the 10.0.12 runtime bundled in Installer 0.3.0, which the .NET 10.0.13 security fixes apply to. This release also brings the Briosa brand v2 design to the app.

Update existing Installer installations to 0.4.0. Updating a system-wide .NET installation doesn't patch the runtime bundled in an older Installer.

What's changed

• Patched .NET runtime. The bundled NETCore and WindowsDesktop runtimes move from 10.0.12 to 10.0.13 (#29).
• Brand v2 (Caliper b).
  • A new void-tile icon for the app, launcher and shortcut that reads on both light and dark taskbars.
  • The Installer compact logo, drawn as vector artwork.
  • The v2 palette: void in dark mode, clean room in light mode.
  • The Scanline measurement-grid background, turned off in high contrast.
  • The Saira font license now ships in licenses/ (#31, #33).
• Release validation. Release packaging now installs, verifies and repairs the published Server 0.9.2 packages for SA 2024.1.0508.5 and 2026.1.0529.7. It does this through the packaged CLI and a disposable signed catalog (#21, #23, #25). Signing uses tools pinned to Briosa v0.9.2 (#27).

Package management, sources, settings, CLI commands and SDK registration work as in 0.3.0. Existing settings and installed server packages carry over unchanged.

Assets and verification

The offline setup and the portable ZIP each come with an adjacent SHA-256 checksum, and the ZIP also has package provenance. First-party binaries, the shortcut script, setup and uninstaller carry timestamped Windows signatures from David Lucas. The release workflow builds source commit 2897d8d04b52a26843b337968640635e0cd40ef3.

Validation covers:

• core/CLI tests and the WPF workflow smoke;
• complete offline packaging;
• installing the real Server 0.9.2 packages for both SA targets;
• signed CLI and launcher checks;
• signed catalog/package interoperability;
• setup lifecycle checks.

These checks don't start SpatialAnalyzer or change SDK registration. The existing enterprise acceptance limitations still apply.

Full changelog

Briosa Installer 0.3.0

What's Changed

• Register side-by-side Briosa installations for client discovery by @davidalucas in #19

Full Changelog: v0.2.2...v0.3.0

Briosa Installer 0.2.2

Briosa Installer 0.2.2 is a security patch that rebuilds the self-contained Installer, CLI, launcher and conventional Windows setup with .NET runtime 10.0.12 using SDK 10.0.401. It replaces the affected 10.0.10 runtime without changing Installer behavior or application dependencies.

Update existing Installer installations to 0.2.2. Updating a system-wide .NET installation does not patch the runtime bundled in an older Installer. Separately update installed Briosa server packages to 0.6.1 for their runtime fixes.

The complete offline setup and portable ZIP include adjacent SHA-256 checksums; the ZIP also includes package provenance. First-party binaries, the shortcut script, setup and uninstaller carry timestamped Windows signatures from David Lucas. The release workflow builds source commit db85f969cb40007f763341234a3f2db560547a01.

Validation covers core/CLI tests, WPF workflow smoke, complete offline packaging, signed CLI and launcher checks, signed catalog/package interoperability, and setup lifecycle checks. No SpatialAnalyzer process is activated and no SDK registration is changed by these checks. Existing enterprise acceptance limitations remain.

Version 0.2.1 was not published because its signing job did not provision the newly pinned SDK. Version 0.2.2 includes that signing setup correction.

Runtime patch #16 · Signing correction #17 · Full changelog

Briosa Installer 0.2.0

Control Center access

Installed Briosa server packages that include Control Center now expose Open Control Center in Installations. The installer verifies the package before opening its status window; the user explicitly starts the server and SDK there.

The new action is included in the signed Windows setup and portable ZIP. Existing packages remain supported, and installation itself does not start a server or change SpatialAnalyzer SDK registration.

What's Changed

• Open verified server Control Center from Installations by @davidalucas in #14

Full Changelog: v0.1.0...v0.2.0

Briosa Installer 0.1.0

Briosa Installer 0.1.0

The first official Windows x64 release of Briosa Installer provides a conventional offline setup wizard and a shared desktop/CLI package manager.

• Download and run the setup EXE from Install Briosa. Setup installs per-user, creates a Start menu shortcut, and registers an uninstaller in Windows Installed apps.
• Choose the Briosa public source or configure an enterprise/offline source before the first catalog request.
• Install exact-SA-target Briosa server packages side by side, verify and repair their files, remove individual versions, and recover interrupted maintenance.
• Review installer updates and intentional rollback in Settings. Setup upgrades preserve downloaded packages and newer installer selections.
• Inspect local SDK setup, review supported registration maintenance, and export Activity diagnostics.

The setup, uninstaller, and first-party executables carry timestamped Windows signatures from David Lucas. The adjacent SHA-256 file verifies the setup download. The ZIP remains available for portable deployment, complete mirrors, and catalog-driven updates. Both distributions include the .NET runtime.

Uninstall retains settings, credentials, and managed server/installer packages. Installing Briosa does not install SpatialAnalyzer, register its SDK, or start a server. Running MP commands requires a separately installed and licensed exact-target SpatialAnalyzer environment.

Validation scope

Validation covers 169 core/CLI tests, WPF workflows and contrast checks, complete final signed package workflows, timestamped executable signatures, and setup installation, reinstall, upgrade/file replacement, downgrade rejection, running-app protection, uninstall, and retained data. Native review covered the wizard, first-use choices, keyboard access, and public catalog verification.

Real Artifactory/proxy environments, standard-user managed rollout, native high-contrast/Narrator, and mixed-monitor DPI acceptance remain unverified. Configure and validate your organization's mirror and deployment environment before rollout. This release does not establish broader SpatialAnalyzer SDK compatibility or vendor installation repair.