Skip to content

Releases: fejdraus/CreatioHelper

desktop-v1.0.32

Choose a tag to compare

@github-actions github-actions released this 24 Jul 08:02

What's new in v1.0.32

Fast Compile

New compile mode that matches what the Creatio web Compile button does: it compiles only the changed schemas instead of regenerating every schema source.

  • Fast Compile = Build + BuildConfiguration -force=False

Measured on a large configuration:

Mode Time
Fast Compile 11 min
Compile 30 min
Compile All 40 min

Requires Creatio 8.0.10 or later — the Build operation does not exist in earlier versions. On older versions the option is disabled in Desktop, and any other entry point falls back to the regular Compile with a warning.

  • Desktop: new Start (Fast Compile) item in the Start dropdown.
  • CLI: new --compile fast value.

cli-v1.0.32

Choose a tag to compare

@github-actions github-actions released this 24 Jul 08:01

What's new in v1.0.32

Fast Compile

New compile mode that matches what the Creatio web Compile button does: it compiles only the changed schemas instead of regenerating every schema source.

  • Fast Compile = Build + BuildConfiguration -force=False

Measured on a large configuration:

Mode Time
Fast Compile 11 min
Compile 30 min
Compile All 40 min

Requires Creatio 8.0.10 or later — the Build operation does not exist in earlier versions. On older versions the option is disabled in Desktop, and any other entry point falls back to the regular Compile with a warning.

  • Desktop: new Start (Fast Compile) item in the Start dropdown.
  • CLI: new --compile fast value.

desktop-v1.0.31

Choose a tag to compare

@github-actions github-actions released this 23 Jul 20:13

What's new in v1.0.31

Compilation

  • Compile now builds the server assembly, not just static content. Previously Compile ran only BuildConfiguration -force=False, which regenerates client static content but never compiles the server C# assembly (conf/bin). Compile now runs RegenerateSchemaSources first, so the server assembly is actually produced:
    • Compile = RegenerateSchemaSources + BuildConfiguration -force=False
    • Compile All = RegenerateSchemaSources + RebuildWorkspace + BuildConfiguration -force=True (unchanged)
  • One compile per package stage, with depth (incremental vs full) taken from the button.

Configuration rollback

  • Read the configuration backup Creatio writes automatically on package install (conf/backup).
  • Roll back to the state before the last package installation.
  • Exposed in both Desktop (button) and CLI (restore command).

Core / build

  • Run shell commands through one runner; fixed three deadlocks.
  • Resolve the Creatio site layout in one place.
  • Bumped NuGet packages to 10.0.10 / latest; hardened the updater version parse.
  • Component-scoped release pipeline: Desktop, CLI and Agent are released separately.

Desktop

  • Redis section made readable instead of a raw attribute dump.
  • Advanced Redis settings block simplified.
  • Exposed the Redis web.config settings required by Redis Cluster.

cli-v1.0.31

Choose a tag to compare

@github-actions github-actions released this 23 Jul 20:12

What's new in v1.0.31

Compilation

  • Compile now builds the server assembly, not just static content. Previously Compile ran only BuildConfiguration -force=False, which regenerates client static content but never compiles the server C# assembly (conf/bin). Compile now runs RegenerateSchemaSources first, so the server assembly is actually produced:
    • Compile = RegenerateSchemaSources + BuildConfiguration -force=False
    • Compile All = RegenerateSchemaSources + RebuildWorkspace + BuildConfiguration -force=True (unchanged)
  • One compile per package stage, with depth (incremental vs full) taken from the button.

Configuration rollback

  • Read the configuration backup Creatio writes automatically on package install (conf/backup).
  • Roll back to the state before the last package installation.
  • Exposed in both Desktop (button) and CLI (restore command).

Core / build

  • Run shell commands through one runner; fixed three deadlocks.
  • Resolve the Creatio site layout in one place.
  • Bumped NuGet packages to 10.0.10 / latest; hardened the updater version parse.
  • Component-scoped release pipeline: Desktop, CLI and Agent are released separately.

CLI

  • Support --key=value syntax and stop losing option values.

v1.0.24

Choose a tag to compare

@github-actions github-actions released this 19 Jul 09:03

What''s new in v1.0.24

Transitional release that prepares the project for independent, component-scoped releases (Desktop / CLI / Agent released on their own versions and tags).

🔧 Auto-updater accepts prefixed release tags

The Desktop auto-updater now recognises both the current v1.0.24 tag format and future component-prefixed tags such as desktop-v1.0.25 and cli-v0.4.0.

This release deliberately keeps the old v1.0.24 tag so that clients already running v1.0.23 can update to it. Once v1.0.24 is installed, its updater can follow the prefixed tags that the next releases will use — no manual reinstall required.

There are no user-facing feature changes in this version; it only makes the upgrade path forward-compatible.


Full Changelog: v1.0.23...v1.0.24

v1.0.23

Choose a tag to compare

@github-actions github-actions released this 13 Jul 18:20

What''s new in v1.0.23

✨ Status bar now shows the database and Redis in use

The status line under the log tells you at a glance which stores the selected site is working with — no need to open the config tab:

App version: v8.1.5.2177 · DB: AstanaMotorsCRM · Redis DB: 12 · Pool: Started · Site: Started · App: Healthy (10 ms)
  • Database name and Redis DB index, read from the site''s ConnectionStrings.config
  • The Redis segment reports Cluster or Sentinel (N) when those modes are configured, instead of an index that carries no meaning there
  • Values refresh the moment you edit the database or Redis settings in the config tab
  • The version is now prefixed with App version:, and the whole line is easier to read

⚡ Faster, cancellable status refresh

  • Each segment appears as soon as its own probe finishes — the version, database and pool state no longer wait for the HTTP health check to complete
  • Switching sites cancels the in-flight probes of the previous site instead of waiting for them to time out, so the new site''s status loads immediately

🔧 UI

  • The Connection Strings tab is renamed to ConnectionStrings.config, matching how the Web.config tab is named after the file it edits

Full Changelog: v1.0.22...v1.0.23

v1.0.22

Choose a tag to compare

@github-actions github-actions released this 13 Jul 12:40

What''s new in v1.0.22

🐛 Fix: Stop button stayed enabled after a deployment

The Stop button remained clickable after a deployment finished, was cancelled or failed — the terminal paths in the deployment orchestrator re-enabled it instead of disabling it. Most visible when compiling a site selected via Folder mode. Present since v1.0.10.

🔧 Skip Restart checkbox is now honest about what it does

  • Labelled Skip IIS Restart in IIS mode and Skip Service Restart in Folder mode, where it applies to the service named in Service Name (typically the Kestrel service), not to IIS.
  • Hidden in Folder mode when no service name is set — there is nothing to restart, so the option had no effect.

⚡ Status bar hardening (introduced in v1.0.21)

  • No more PowerShell processes: IIS pool and site state is now read in-process via ServerManager instead of spawning two powershell.exe per 10-second tick. Also works without elevation.
  • No UI stalls: filesystem probes (site version, appsettings.json) moved off the UI thread — a slow or disconnected network/subst drive no longer freezes the window on every tick.
  • No stale statuses: switching sites clears the statuses immediately, so the previous site''s Started/Healthy is never shown for the newly selected one; results whose target changed mid-flight are discarded.
  • A tick is skipped while the previous refresh is still running; the working health endpoint is cached per URL.
  • The polling timer is stopped when the main window closes.
  • The cached site version is reset on site path change, so an in-place upgrade is picked up (it also feeds DeploymentOptions.SiteVersion).

📖 Documentation

README and User Guide now document the Connection Strings tab and the status bar.


Full Changelog: v1.0.21...v1.0.22

v1.0.21

Choose a tag to compare

@github-actions github-actions released this 13 Jul 09:26

What''s new in v1.0.21

✨ New: Local site status bar

A live status line under the log output on the Deployment tab, showing the state of the currently selected site:

  • Creatio version of the selected site (e.g. v8.1.5.2177)
  • IIS mode: application pool and site state (Pool: Started · Site: Started)
  • Folder mode (Kestrel): optional Windows/Linux service state; app URL is resolved automatically from appsettings.json Kestrel endpoints
  • App health: HTTP check against the application''s /ping endpoint (fallback to the site root) using the real scheme, host and port from the IIS site binding — catches the case where the pool is running but the application itself is down (App: Unhealthy / No response)
  • Color-coded: green when healthy, red when not, orange/blue for transitional states
  • Refreshes on site selection, mode change and automatically after each deployment

Full Changelog: v1.0.20...v1.0.21

v1.0.20

Choose a tag to compare

@github-actions github-actions released this 12 Jul 13:41

What''s new in v1.0.20

✨ New: Connection Strings editor (Desktop)

New Connection Strings tab for editing ConnectionStrings.config of the selected site:

  • Smart per-field editing for db, redis, messageBroker, elasticsearchCredentials, influx, s3Connection and path entries — no more hand-editing raw strings
  • DB type auto-detection from Web.config / Terrasoft.WebHost.dll.config (executorType): MS SQL Server, PostgreSQL and Oracle formats are all supported, including Oracle TNS descriptors and Integrated Security strings
  • Redis mode dropdown: Single node / Cluster (Creatio 7.18.0+) / Sentinel (deprecated, hidden on 7.18.3+). Cluster nodes are edited as a host:port list with add/remove buttons
  • Key-preserving merge: unknown parameters (Pooling, Max Pool Size, maxReadPoolSize, useTls, ...), quoting and key order survive edits; each section exposes an editable Other parameters field
  • Fill-what-you-want philosophy: existing settings are loaded on open; missing entries are created on save only when their fields are filled — empty sections never touch the file
  • Site version is resolved from Terrasoft.Common.dll in Folder mode, so version-gated options work without IIS

🐛 Fixes

  • NumericUpDown fields no longer show a binding validation error when cleared (all numeric fields, including the Web.config HTTPS port)

🔒 Security

  • Override SQLitePCLRaw.bundle_e_sqlite3 to 3.0.3 to resolve GHSA-2m69-gcr7-jv3q (high severity, bundled SQLite)

🔧 Dependencies

  • Swashbuckle.AspNetCore 10.2.3, LiveChartsCore 2.0.5, Mapster 10.0.10, Grpc.Tools 2.82.0, System.Management.Automation 7.6.3, StackExchange.Redis 3.0.17, Microsoft.Data.SqlClient 7.0.2, MudBlazor 9.7.0, Microsoft.NET.Test.Sdk 18.7.0

Full Changelog: v1.0.19...v1.0.20

v1.0.19

Choose a tag to compare

@github-actions github-actions released this 19 Jun 11:54

What's new in v1.0.19

Fix: WorkspacePreparer lic path resolution

Fixed sourcePath="." bug when a relative path was passed to LoadLicResponse — now resolved to absolute before splitting into directory and filename.

Fix: FileDesignMode buttons appear immediately on startup

Cached SelectedIisSitePath in settings so RefreshFileDesignMode can run early, before the async IIS site enumeration completes.

Improvement: Incremental install available when packages folder is selected

The Start button is now always a SplitButton — click for incremental install (packages + BuildConfiguration -force=False), dropdown for full rebuild. Previously, selecting a packages folder forced full rebuild with no choice.

Removed: Splash screen

Removed the splash screen — it appeared too late (after .NET single-file extraction) to be useful, and DI initialization is fast enough to not need it.


Full Changelog: v1.0.18...v1.0.19