Skip to content
This repository has been archived by the owner on Jul 1, 2020. It is now read-only.

Creating Patches

Süleyman Yasir KULA edited this page Mar 7, 2020 · 33 revisions

Prerequisites


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 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. During the integration phase, if you've used UseVersionInfoVerifier/UsePatchInfoVerifier to verify the downloaded patch files using a public RSA key, then sign your patch file(s) with the private RSA key
  6. Update the VersionInfo.info at versionInfoURL

B. Using legacy method

Click here to show/hide

  1. If this is a self patching app, create a self patcher and put its files inside a subdirectory called SPPatcher in your application directory (built project)
  2. Generate the patch
  3. If your previous patch had any <IncrementalPatch>es in its VersionInfo, copy them to the newest VersionInfo (only 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. During the integration phase, if you've used UseVersionInfoVerifier/UsePatchInfoVerifier to verify the downloaded patch files using a public RSA key, then sign your patch file(s) with the private RSA key
  7. Update the VersionInfo.info at versionInfoURL

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

Clone this wiki locally