Version Upgrade Steps

Step 1

Create a separate branch for upgrading from the stable version. The benefits of doing this branching structure are regular work will not be hampered.

Step 2

Download the latest SDK from GitHub (say for example V9.7.1) that needs to be merged to the Project SDK solution (say for example V9.6.2.x). 

The link to the GitHub Repository to download the SDK code is given below

https://github.com/amlacommerce/znode/releases

Step 3

Compare the SDK solutions of the current and the new version in GitHub to know the number of files that have been modified. Copy the list of file names separately (in a notepad or excel) to track the manual merge of the files. The relevant snapshot to do the comparison is shown below

Step 4

Merge entire files for API projects.

Step 5:

Merge all the views in Admin as well as in Webstore (For webstore recommended to merge Default themes views.)

Step 6:

Merge all the .ts files in a Script section of Admin and Webstore. (Don’t merge .js file and map files)

Step 7:

Merge the Znode.Library.Resources for newly added resources from upgrade code.

Step 8:

Merge the Znode.Library.Resources for newly added resources from upgrade code.

Step 9:

Compare the web. config files of Admin, API, and Webstore to check if any new key has been added in it, if so then add such changes.

Step 10:

Upgrade the latest package files from nuget package.

Step 11:

Upgrade the latest package files from nuget package.

Step 12:

Run the upgraded db script on Database provided with the upgrade code.      

Before you execute the scripts, ensure that you have not modified any of the base DB scripts (like SP, Triggers, Views) for your project purpose. In case you have modified any of the Base scripts, then do a manual comparison of those scripts, merge the code as necessary, and then execute the scripts.

Notes:

After completion of the above-mentioned migration steps, build the solution. On successful build, run the solution and verify the functionalities. Please ensure to validate the below-mentioned points

1. If you have already made changes in the base functionality (in views, .ts) then merge them properly
2. Validate the existing functionalities
3. Validate if the functionalities expected in the patch are working fine. If so, close the appropriate ZLMC tickets.
4. Ensure the upgrade didn’t break any of the existing functionalities.