What's new in Cloudhouse release 1903

Save to PDF

Applies to: AppAcceleratorV, Auto Packager, Container Editor, and Cloudhouse Containers

06/06/2019 Cliff Hobbs   ID: 390913

Overview

Release 1903 is now available from Cloudhouse.

This topic details the new features and fixes for the Cloudhouse AppAcceleratorV, Auto Packager, Editor, and the Cloudhouse Compatibility Containers™ they create released throughout March 2019.

Any components changed this month are version 4.5.1903.nnnn  and 4.6.1903.nnnn as a major new release of the Cloudhouse components were released on 26th March, as detailed below.

AppAcceleratorV

New Features

AppAcceleratorV 4.5.1903.23228 (released 14th March 2019)

Auto Packager

New Features

Auto Packager 4.5.1903.23846 (released 18th March 2019)

  • The version number of the Auto Packager is now shown in the bottom right-hand corner.
  • Publish to portal functionality has been removed

Auto Packager 4.5.1903.23836 (released 14th March 2019)

  • Replace the content of the returned response in Browser compatibility.

Fixes

Auto Packager 4.5.1903.23846 (released 18th March 2019)

Resolves:

  • Packager crashing on Windows XP
  • An XP issue when iterating service user privileges
  • Cloudhouse.Stub.exe is no longer flagged by AV
  • HKEY_CURRENT_USER\SOFTWARE\Classes\Folder has been excluded from redirections
  • A crash when a captured registry value contains invalid XML chars.

Auto Packager 4.5.1903.23836 (released 14th March 2019)

Resolves:

  • Cloudhouse.Container.Run.exe not running on Windows XP
  • Infinite recursive directory being created if the period "." was specified as the value for /deploydir

Container Editor

Note

Updating a deployed Container created with version 4.5 of the Cloudhouse tools to version 4.6 is unsupported and will result in an error. To update a version 4.5 Container to version 4.6, you need to uninstall version 4.5.x of the Container Editor and install version 4.6.1903.1001 or later.

Fixes

4.6.1903.1001  (released 26 03 2019)

Resolves:

  • A crash when updating AAV components and the AAV versions folder does not exist.

Cloudhouse Containers

New Features

4.5.1903.1156 (released 14 03 2019)

  • Adds /force flag for deployment to uninstall any existing deployments and clear deploydir
  • Usage reporting now includes the versions of AAV and Container components.
  • Allows COM to be uninstalled even if the EXEs are missing.

4.6.1903.1198 (released 26 03 2019)

Resolves:

  • A deployed Container from being deleted if the /Update switch is used.
  • /Update switch will not allow version 4.5 Containers to be updated to version 4.6. due to COM virtualisation changes (the old Container must be uninstalled first).

Fixes

4.5.1903.1156 (released 14 03 2019)

Resolves:

  • An issue that caused incorrect error messages to be logged.
  • An issue where a Container deployment into itself was permitted and caused recursive deployments.
  • An issue where that same COM GUID in HKLM and HKCU will cause a deployment to fail.
  • An issue where a '/' in the deploydir would deploy the file system correctly (with '\') but the registry would contain the invalid path.
  • COM configuration issues where 64 and 32-bit localserver32 conflicted.

Deprecated or Removed Commands

  • Publishing to the portal from the packager

Advisories

Advisory 1

The Container Editor should only be used to update applications, file, and registry redirections on the same architecture the original Container was created on. For example, if the Container was created on an x86 machine, then the Container Editor must be run on an x86 machine to update the Container.

Anti-Virus Advisory

Remove any Runx.exe files (where “x” is a number), from the Container before deploying it. These files are only required if you need to create Universal Windows Platform (UWP)/MSIX packages of the Container. Anti-virus and malware scanners may flag these files as malware as they are unsigned and designed to run other executables.

Features in Upcoming Releases

See Planned features for future Cloudhouse releases for details of the features we have planned for future releases of our products.

Source:
Was this article helpful?

Table of Contents

    Can't find what you're looking for?

    Contact Support