In an effort to make keeping your VDI images and FlexApp Packaging Console in sync with a common and consistent set of runtime versions, we have released a bundled installer with the most common runtimes included.
Microsoft .Net 3.5.1
Microsoft .Net 4.8
Microsoft Visual C++ 2005 Redistributable (x86) - 8.0.61001
Microsoft Visual C++ 2005 Redistributable (x64) - 8.0.61001
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161
Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.6161
Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219
Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219
Microsoft Visual C++ 2012 Redistributable (x64) - 11.0.61030
Microsoft Visual C++ 2012 Redistributable (x86) - 11.0.61030
Microsoft Visual C++ 2013 Redistributable (x64) - 12.0.40660
Microsoft Visual C++ 2013 Redistributable (x86) - 12.0.40660
Microsoft Visual C++ 2015-2019 Redistributable (x64) - 14.25.28508
Microsoft Visual C++ 2015-2019 Redistributable (x86) - 14.25.28508
Microsoft Visual J# 2.0 Redistributable (x86) - 1.0
Microsoft Visual J# 2.0 Redistributable (Second Edition x64) - 1.0
Download:
https://cdn.liquidware.com/FlexApp/RuntimeInstaller-1.1.0.exe
Installation:
Basic:
Right-click, Run as Administrator - Reboot manually once complete
Advanced CLI Options:
-d Set logging level to Debug
-h *This help information
-l The filename and path to use for logging
-n *Check if ANY of the included runtimes are NOT installed
Returns 1 for true, 0 for false
-o *Check if the OS requires a reboot
Returns 1 for true, 0 for false
-q Suppress output to the command line
-r Restart the machine if any of the runtimes require it
-u Attempt to uninstall c++ runtimes older than those included
*These 3 options only work after a manual extraction; -h -n -o
Details:
-q quiet, no command line output and no popup
Note: there is no visual clue that the tool is done in this mode; check the log file for “PackageRuntimeTool finished."
-r if a restart is required by the runtimes installed, it will be forced
-l <logpath> provide a custom filename and path to log to
(default: log file is created wherever the PackageRuntimeTool is run from)
Note: a logfile is always created but will not be available unless given a path (the default is useful when using the tool outside of its packaging)
0 Comments