General information about the patch.
Short description of the patch. It usually contains the product's name.
The full name of your company.
A more detailed description of the application.
Allow Product Code mismatches
The target and upgraded images may have different Product Code. By setting this option you will be able to create a patch between them (normally the target and upgraded packages must have the same Product Code).
Allow Product Version major mismatches
The Product Version's first (major) field may differ between the target and upgraded images.
Don't remove temporary folder when finished
Useful for debugging.
Include whole files only
As opposed to creating binary file patches. The patch will be bigger but it will run faster. Also, if a file has changed in the Upgraded package, the whole file will be included in the patch (not just the differences between the old file and the new one).
Optimise patch size for large files
Patches for files greater than approximately 4 MB in size may be made smaller.
Disable automatic patch sequence information generation
Prevent the automatic generation of patch sequencing information, by setting the value of the SEQUENCE_DATA_GENERATION_DISABLED property to 1 in the Properties Table of the .pcp file.
If you make changes in the Patch Sequence view, the SEQUENCE_DATA_GENERATION_DISABLED property will be ignored.
Patches to replace
These patches, if found installed and registered with Windows Installer on the user's computer, will be unregistered from the appropriate places.
Use thebutton to add a patch to replace, the button to replace one or the button to remove it.
Although the path to the MSP file will be stored here, only the GUID will be extracted and written in the final built patch.