Creating Patches

Prerequisites

• take a look at the Glossary to familiarize yourself with the terms that are used throughout the wiki
• integrate SimplePatchTool, if you haven't done already
• see the Recommended Project Structure

---

There are two ways to create patches:

A. Using ProjectManager (recommended)

Click here to show/hide

If you were using the legacy method to create patches, you can easily migrate to ProjectManager.

1. Create a project (if you haven't already done so)
   • See About Projects to learn more about the structure of your project and customize its settings
   • If this is a self patching app, create a self patcher executable and put its files inside the project's SelfPatcher directory
2. Generate the patch
3. Upload the patch files to the server of your choice
4. Update the download links in VersionInfo
5. If you've embedded a public RSA key to your application during the integration phase to verify the signatures of your patch file(s) for increased security, then sign your patch file(s) with the private RSA key
6. Update the VersionInfo.info on your server

B. Using legacy method

Click here to show/hide

1. If this is a self patching app, create a self patcher executable and put its files inside a subdirectory called SPPatcher in your application directory
2. Generate the patch
3. If your previous patch had any <IncrementalPatch>es in its VersionInfo, copy them to the newest VersionInfo (if they weren't copied automatically)
4. Upload the patch files to the server of your choice
5. Update the download links in VersionInfo
6. If you've embedded a public RSA key to your application during the integration phase to verify the signatures of your patch file(s) for increased security, then sign your patch file(s) with the private RSA key
7. Update the VersionInfo.info on your server

After you create a patch, a file named {PROJECT_NAME}_vers.sptv will automatically be created in the new version's directory. This file simply stores the version of the application.