|What's new in version 1.4|
This document describes changes in SharpSetup 1.4 conpared to previous version (1.2).
SharpSetup 1.4 introduces major enhancements to its bootstrapper.
IntermediateBootstrapper project allows you to execute custom C++ code prior to main GUI which is necessary when .NET Framework or another prerequisite of main GUI is not installed. In version 1.2 this project produced .exe file which was executed after unpacking files. Version 1.4 keeps the main concept but changes format from .exe file to .dll file. This change allows for better integration between Bootstrapper and IntermediateBootstrapper (eg. reporting status or progress).
To ease common tasks that have to be implemented in IntermediateBootstapper's C++ code new library is provided with SharpSetup 1.4. It allows you to query registry, check if specific product is installed, set progress, display message boxes, write to installer log, etc. As an example functions that check for and install .NET Framework and Windows Installer have been implemented.
File providers are classes that take care for locating files that are needed for prerequisite installation. SharpSetup 1.4 comes with 3 providers:
Format of the configuration file has been changed from line based text file (mainconfig.txt) to XML file (configuration.sscf). New file format has clearer structure and allows for IntelliSense to give hints about specific configuration tags. It also allows preliminary checking of configuration correctness in Visual Studio even before you start to build the solution.
SharpSetup 1.4 fixes many bugs that existed in version 1.2. This includes both issues reported by users and ones detected internally.
Previous versions of SharpSetup had problems when installers were run on devices with non standard DPI settings (images were not scalled well, controls were not properly resized in certain cases). These problems were fixed in version 1.4.
After releasing version 1.2 of SharpSetup several problems have been reported that related to missing third party components such as C++ support in Visual Studio or lack of VS integration component in Windows Installer XML. This resulted in cryptic error messages. Version 1.4 makes these messages much clearer.
List of other bug fixes: