What's new in Cloudhouse release 1712
16/01/2019 Cliff Hobbs
Release 1712 is now available from Cloudhouse.
New features and fixes for the Auto Packager, and the Containers created by the Auto Packager. All changes detailed have been released throughout December 2017.
New Features In Containers
- EULA must be accepted during Container deployment with the /AcceptEULA switch. Please note, if you have upgraded Cloudhouse components e.g. Cloudhouse.Container.Deployment.exe in an existing Container then please copy EULA.html from the Auto Packager root directory into the Container.
- The November 2017 EULA will be added to all Containers created after the 21st of December.
Fixes in Containers
- Container telemetry reports whether DeploymentScript.xml are used to perform install /uninstall tasks.
- Stub executables create log files in user local appdata folder (same directory as the Container's other log files).
- AAV debug files are now written to %LocalAppData%\Cloudhouse\AAV with a file name of <reverse-timestamp>-<ExeName>-<pid>
- AAV unable to load DEPOpt-Out feature in AAV build 22487, caused by migration to Visual Studio 2017 and bug in ANSI handler.
New Features In Auto Packager
- Updated with latest November 2017 EULA.
- Auto Packager inserts the latest EULA into all new Containers.
- Container Editor - Undo / Redo for operations on the File tab.
- Package Editor - Spinner shows progress during long running tasks for undo/ redo and add/ remove tasks.
- Upgrade to latest Package Editor removes files that are no longer required.
Fixes in Auto Packager
- Auto Packager crashes packaging applications on Windows XP and 7. This was caused by files without a date modified stamp.
- Package Editor - Optimize loading of the registry and directories when editing Containers.
- Package Editor - Registry view - no longer crashes when selecting a Reg Value.
- Package Editor - No longer crashes when updating snapshots because it could not find file 'C:\Documents and Settings\User\Desktop\ExclusionList.json'.
Cloudhouse recommends using the Auto Packager on x86 operating systems only, re-directions will not be created correctly for applications that contain a mix of x64 and x86 components. Containers will be created successfully for applications that contain only x64 components, but successful packaging on this platform requires detailed knowledge of the application prior to packaging.
Features in Upcoming Releases
See the Features in Upcoming Releases page for details of the features we have planned for feature releases of our products.