Release 7.1.2
Improvements
- Improved validation of linked expressions in configuration file editor.
- Added an environment variable
BDEPLOY_LAUNCH_MODE
which is set toPATH
orASSOCIATION
(or not set at all by default) depending on the way the application was launched (e.g. as a script from thePATH
, or through file association, e.g. double-click). - Added the possibility to specify a target system when creating instances from instance templates via the CLI.
- Windows applications have been updated from the outdated .NET 4.5.2 to a still supported 4.7.2
Warning
On very old Windows versions this may now require .NET 4.7.2 to be installed. Affected Windows versions have been out of support for a long time, so this is not considered a breaking change. 4.7.2 is pre-installed since Windows 10 build 1803 (April 2018). - A lot of further code quality improvements internally.
Fixes
- Fixed an issue where client application uninstallation would not remove association to scripts and file extensions properly.
- Fixed the situation where client applications launched through a script would not correctly propagate their exit code.
- Fixed an issue which caused the windows cmd to remove
%
signs from the passed parameters erronously. - Fixed an issue where the Install button of an instance which was never installed before was enabled despite the product being missing (because it was deleted after creating the instance).
- Fixed an issue where a
\
given in the path name of a data file would lead to a file that cannot be deleted anymore. - Fixed an issue where the client launcher would try to update itself (and fail) when starting an
offlineStartAllowed
client application whilst being offline.