 |
 |
 |
| Patch Manager Main Window with empty project. |
New Project is Created by selecting the New Project menu Button. |
Enter the Project name into the Project Properties dialog. |
 |
 |
 |
| Optionally enter any comments or notes in the memo tab. |
After the new project is created, select the version menu and click "New Version" to create an instance of a version for program being distributed. |
The Version Properties dialog will allow you to set the version for this bucket that will reference a version of a file or multiple files to be patched. |
 |
 |
 |
| After the version has been added, files that belong to that version must then be added. |
The file properties will dialog will prompt you to select the file. The second option will set the destination install path which can be a value from the registry, an absolute path or a system path. |
Aliases: This illustration shows how aliases are used to manage patches as opposed to hard coding a patch. Select the Add Patch option under the files properties for version. |
 |
 |
 |
| The Aliases lookup dialog will popup. Since there are no Aliases in this system, we will add one by select Add. |
Stage 1 of Alias wizard prompts us for the Alias Name. We enter the ASTACLIENT and select NEXT. |
Stage 2 prompts for where the program location will be obtained from. We will select the Registry and proceed. |
 |
 |
 |
| This shows that 1 executable file with the indicated name, size and date has been added to the version 1.0.0.0 bucket. Additional files may be added by simply selecting the Files -> Add option in the main menu. |
Stage 3 will allow us to select where to look in the registry for the patch location. We specify a sample registry location which contains a string value of our test Asta Client location "C:\ASTATEST". |
After finishing our new Asta ALIAS add operation, then we can select it for use. |
 |
 |
 |
| The hard coded path is now using the alias "%ASTATEST%". This alias can be used for the different versions and will reduce data entry,minimize typographical error and help maintain consistent installation paths. |
This example shows the addition of a new version into the project. The procedure are identical to version 1.0.0.0. |
The version number is incremented by 1 to show a reflect a new and unique version. |
 |
 |
 |
| Files are added by highlighting the new version and selecting Files->Add. |
The select file dialog will allow the standard browsing of the correct path and files. |
Files are now added to version 2.0.0.0. |
 |
 |
 |
| Files are now added to version 3.0.0.0 |
After the versions and files have been properly created and configured, the patch file that will be distributed will have to be created. This can be done by going to Patches and selecting New Patch Wizard. |
When Stage 1 of the Patch Wizard dialog appears, it will show available versions and ask the user to select the target version that the patch will create. Target version need only be highlighted and then proceed by selecting NEXT. |
 |
 |
 |
| Stage 2 of the Patch Wizard Dialog will display versions to select the source that the patch will be able to update from. Source version(s) need only be highlighted and then proceed by selecting NEXT. Notice that the target version does not appear. |
Stage 3 prompts the user to select the target path and name for the new patch file and gives the option of building the patch immediately after selecting finish. Since this is the final stage, the options are to finish or to go back and make revisions. |
Since the Build Patch Now was checked, the build process will begin immediately and show a progress dialog to show the progress of the patch. The build process can be cancelled at any time during the build process. |
 |
 |
 |
| When the build is finished. The Progress dialog will indicate success. |
The patch build is now saved with the specified settings and ready for regeneration. Notice that multiple patch build templates with different configurations can be created and stored. |
The script window on the right hand side will show step by step what the currently highlighted patch will do. |
 |
 |
 |
| Additional functionality can be appended into the script for further processing outside of the standard patch process. This is achieved by right clicking and selecting insert to add a new step in the patch process. |
The following dialog shows what is available to append in the script which is wizard driven. |
The following shows that a comment was added to the script indicating that it is a test script entry. |
Products 
