CobbleConnect™ – Application Update Guide
Overview
CobbleConnectâ„¢ provides multiple supported ways to keep the application up to date. All update mechanisms are based on the Advanced Installer updater and follow enterprise deployment, security, and compliance best practices.
Update Method 1: Automatic Update on Application Launch
When CobbleConnect starts, the application can automatically check for updates before the main UI loads. This is typically handled by a startup batch or script configured during deployment.
How it works
1. The user launches CobbleConnect.
2. A startup script or batch executes first.
3. The script launches updater.exe.
4. If an update is available, the updater applies it and restarts the application.
5. If no update is available, the updater exits and the application opens normally.
Update Method 2: Manual Update from the Application (Support → Updates)
CobbleConnect allows users to manually check for updates from inside the application UI.
How it works
1. The user navigates to Support → Updates.
2. The user clicks Check for Updates.
3. CobbleConnect launches updater.exe from the installed application directory.
4. The updater checks the configured update feed.
Important Behavior During Manual Updates
If an update is available:
- The updater prompts to apply the update.
- CobbleConnect closes automatically to release files.
- The update is installed using a signed MSI.
- The application can then be restarted on the new version.
If no update is available:
- The updater exits automatically.
- CobbleConnect remains open.
- A message indicates the application is already up to date.
Update Method 3: MSI Updater Shortcut (IT-Managed)
When CobbleConnect is installed via MSI, an additional shortcut named 'Updater' is created as part of the installation.
This shortcut is intended primarily for IT administrators and support teams. It allows updates to be executed independently of the main CobbleConnect application.
How it works
1. IT or authorized personnel launch the 'Updater' shortcut.
2. The shortcut executes updater.exe directly.
3. The updater checks the configured update feed.
4. If an update is available, it is applied using the signed MSI.
5. If no update is available, the updater exits with no changes.
Typical Use Cases
- IT-managed update validation
- Updating machines before user login
- Controlled rollouts in restricted environments
- Troubleshooting or recovery scenarios
Why the Application Closes During Updates
When an update is applied, CobbleConnect must close to prevent file locks and ensure a clean replacement of application files. This behavior is required for safe and reliable MSI-based updates and is standard in enterprise desktop applications.
Security and Enterprise Compliance
- All installers and updaters are digitally signed.
- Updates are delivered via MSI packages.
- The updater runs as a separate process.
- No hot patching or in-place binary replacement is performed.
- Compatible with locked-down and IT-managed environments (e.g., GCC High).
Summary
CobbleConnect supports three complementary update approaches: automatic updates at launch, manual updates from within the application, and an IT-managed updater shortcut provided by the MSI installation. All approaches rely on the same secure, enterprise-approved update mechanism.