Upgrading v7 - Initial Code Upgrade

« Return to Notes Listing

Author:Aaron S.
Last Updated:September 02, 2021 5:15 PM

Overview

The steps below are the for the initial code upgrade for 7.0. The goal of this section is to identity any dependency not yet upgrade to 7.0 or customizations that need to be upgraded for a client.

 

Upgrade SDK

  1. Identity customizations or other package dependencies by looking at SDK.Config.json. There are potentially new packages to build or features to migrate for customizations that have become packages such as using the Cart package etc. instead of leaving a legacy customization. 
    1. Each package listed needs to have a v7.0 version: 
      {
      "internalName": "NWS.Titan.Base",
      "minimumVersion": {
        "majorVersion": 6,
        "minorVersion": 9,
        "buildNumber": 5,
        "revision": 0
      },
      "maximumVersion": {
        "majorVersion": 7,
        "minorVersion": 0,
        "buildNumber": 0,
        "revision": 0
      }
    },
    {
      "internalName": "NWS.Titan.Blocks",
      "minimumVersion": {
        "majorVersion": 6,
        "minorVersion": 9,
        "buildNumber": 5,
        "revision": 5
      },
      "maximumVersion": {
        "majorVersion": 7,
        "minorVersion": 0,
        "buildNumber": 0,
        "revision": 0
      }
    }
}
    2. In the above example, the only packages are Titan Base and NWS.Titan.Blocks. In this instance, confirm that there is a v7 version of the NWS.Titan.Blocks package.
    3. If not upgrade existing v6.9.5 package to v7.0 by following the Upgrading packages section. 
  2. After confirming all packages are upgraded v7.0, Upgrade the SDK. The Public SDK is a package like any other package, it just contains all legacy client customizations in one SDK instead of sepearted into unique packages. Follow the Upgrading packages section for details.
    1. For all customizations in Public SDK, upgrade to be compatible with 7.0. See Refactoring Code section for details.
top