Getting Started: Creating New Patch

To add Patch module select Patches node inside the desired Version node within Product tree and select Patches node within Product tree and choose from menu {Patches > New Patch}.

 

 

This will invoke "New Patch" dialog (the screenshot you can see below).

 

 

Dialog options:

 

· Patch Name:

Enter the Patch Name you want to build. Patch name cannot be changed after patch creation.

Patch Name must form a valid name of file thus using of such symbols as < > : " / \ | * ? is not allowed.

 

· Patch Type:

Enter Patch Type: Version-to-version or Cumulative.

Refer to the "Concepts and definitions" section for more information concerning Patch types in terms of PatchFactory.

- Use Version-to-version patch type if you want to make a patch module that updates one old version to the current one.

- Use Cumulative patch type if you want to make a patch module that updates several old versions to the current one.

 

After pressing OK button a New Patch is created. Now you're ready to view/edit essential patch options.

 

 

Dialog options:

 

· Patch Name:

Patch Name which you have specified at the previous step.

 

· Patch Type:

Version-to-version or Cumulative.

 

· Allow df:

Set to YES (default) if want to use difference between files of the same name during update procedure.

If set to NO then full copies of new files are used if they differ from old version files.

 

· Allow update on reboot:

Provides replacing of files to be updated at system restart (most often if they are occupied by other processes). YES by default.

 

· Allow uninstall on reboot:

Provides replacing of files to be uninstalled/repaired at system restart (most often if they are occupied by other processes).

 

· Uninstallable:

If set to YES, the backup copy of all replaced/modified files (for which backup is allowed) is saved and a record is added into Add/Remove programs list.

If set to NO then rollback/uninstall of the patch after its successful applying is impossible. Backup copies of files are stored in the temporary folder during patch applying only to provide rollback if an error occurred during patch applying to maintain an old version operating.

 

· InnoSetup script:

Name of the InnoSetup script file used to generate the update module. "default.iss" by default.

 

· Directory:

Folder where the output update modules are saved to.

 

· File name Template:

Template of update modules names.

 

Refer to the "Concepts and definitions" section for more detailed description concerning Patch parameters in terms of PatchFactory.

 

 

And at last we are ready to build the Update Module.

 

To build the Update module select "Patch module" node inside the desired Version's "Patches" node within Product tree and click on the Build Patch button or select Patches node within Product tree and choose from menu {Patch > Build Patch}.

You can also right-click with your mouse on the Patch module node you want to build within Product tree and select "Build Patch" from drop-down list.

 

 

Pressing the Build Patch button initiates the patch building progress dialog to appear:

 

· Operation indicates execution progress of the current operation. (blue-coloured progress bar indicates the similarity ratio of the current old version file versus new version file during their comparing).

 

· Jobindicates execution progress of the current job..

 

· Priority – indicates current system priority of the task.

 

To pause patch building process press "Pause" button.

To cancel patch building process press "Cancel" button.

 

 

Converted from CHM to HTML with chm2web Standard 2.75 (unicode)