Certain aspects of the package (like Custom Actions running in the UI or the Immediate sequence) can be troubleshooted and tested only once an actual MSI installation is started. The problem is that performing a full Installer session and, thus changing the current state of the machine by the Windows Installer engine, is not desired. Especially when not on a Virtual Machine.
The solution to this problem is to trigger testing from PackDesigner. RayPack prepares a build which is similar to an actual package, with the following differences:
1.In order to speed the process up, building of CAB files and medias is skipped
2.The installation sequence is adjusted to prevent any deferred system changes to be written.
Effectively, this means that while the installation runs as normal (and even displays the progress bar of the installation) no changes are actually made to the system, and so the package can be tested many times in a row.
|
Be aware: Standard Windows Installer functionality and well-designed Custom Actions are only making system changes by writing to a deferred execution in-script. Sometimes however, poorly developed packages may contain certain actions that do not respect this rule, for example by changing the local system directly from the UI Sequence. These changes may affect the local system. |
In Order to Test the Package
1.Open any supported package file (RPP, MSI, or MST) in PackDesigner
2.Press button Test in the bottom part of the screen
3.Alternatively, use F8 keystroke to achieve the same
4.A quick build of the package without CAB/Medias will be created
5.After building is finished, the installation routine will be started automatically
6.After closing the Windows Installer session, either by canceling or finishing, a Windows Explorer window will be shown and the log file from the installation will be automatically highlighted.
|
Tip: By default, a log is created in _Logs subfolder and verbose logging options (/l*v) are used. These settings can be configured by manually adjusting the XML file of the selected RayPack profile. Additionally, using the same technique it is possible to disable log generation completely. |
