Versions Compared

Old Version 3

changes.mady.by.user user-eb51a

Saved on

compared with

New Version Current

changes.mady.by.user user-eb51a

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • A Patch is typically used to apply modified compiled objects, shortcuts and executables. You should NOT use a patch to deploy database changes as they are complex to manage and can easily result in a corrupted database, though a Patch Installer file does support this if you understand the risks involved.
  • A Patch is identified by its Patch Number. The Patch number has a direct relationship to the Version or Patch it was based on, for example Patch 1.0.0.1 would be the first patch against Version 1.0.0.
  • To create a Patch, copy a parent Version or Patch. In this way the Patch inherits the parent definition including the objects to be deployed.
  • When the Patch is built, a full MSI file is built in exactly the same manner as the parent Version or Patch was built. The resulting MSI file is compared with the Version's MSI file to produce a difference file – the MSP file. The MSP file may be referred to as a Patch Installer file.
    Note
    Note: Only the Patch Installer file is installable. The interim MSI is deleted once the MSP has been constructed.

...