Skip to content

ELKA EventLens 0.1.0-dev.3 - Development Preview

Pre-release
Pre-release

Choose a tag to compare

@torment78 torment78 released this 29 Sep 17:48
· 1 commit to main since this release

ELKA EventLens 0.1.0-dev.3

Development preview. Not a stable release.

Added

  • Settings > Check for updates, with version information, download progress, cancellation, and SHA-256 verification.
  • Installed copies can download a newer installer, request confirmation, save and exit, update, and reopen. Windows elevation must still be approved. Cancelled elevation or failed downloads leave the app open.
  • Portable copies download a verified ZIP and open its folder. They remain portable and never run the system installer.
  • One-time storage migration completion: old settings, event history, logs, and browser storage move to the ElkaSoft layout. Once migration succeeds, future launches no longer read or import the obsolete folders. Blocked migrations remain retryable; existing destination data is never overwritten.

Install This Preview

Download ELKA_EventLens_Setup_0.1.0-dev.3.exe, or extract ELKA_EventLens_Portable_0.1.0-dev.3.zip. Checksums are in SHA256SUMS-0.1.0-dev.3.txt.

Older builds have no update button, so install this preview manually once. Exit old EventLens copies from the tray first. To switch cleanly from the old Elka Software program folder to C:\Program Files\ElkaSoft\ELKA EventLens, uninstall the old version before installing this one; saved data is retained. Otherwise, Setup preserves the existing installation directory.

Windows 10/11 x64; .NET is bundled. Embedded browsing needs Microsoft WebView2. Setup installs that runtime if missing (internet required). Preview executables remain unsigned.

The local suite passes 103 checks covering migration, updater validation/error handling, layout, browser behavior and existing features. A real public release download was also checksum-verified without executing it. The installer wait/install/restart path passed an isolated smoke test using a separate installer identity and a harmless test executable, followed by uninstall cleanup. Actual third-party login sessions and the production UAC approval flow were not used in testing.

See updating and storage migration.