CLICK 5.6 patch matching

It took us five tries to create an application patch on our development CLICK 5.6 system that would apply successfully to our staging server, with a newly restored copy of our production site running.  Then it took two more smaller patches, with a number of iterations on each, to completely move the new features.

Under version 5.5.3 and earlier the "Version Information" screen included the exact name of the patch file, and I could compare the file name to the names of patch files we've accumulated on our development and staging servers.  In 5.6 we must use the "Patch ID" in the PatchHistory.entity.xml in the patch itself, inside the PATCH.ZIP.  I compare this ID to the PatchID in the left column of Version Information on the staging (patch test site).  This number is a 32 character alpha-numeric that seems to be like a guid.  Each patch has a unique one, so we will not confuse patch files again (not that I've ever made a mistake on a patch).

Version Information:

PatchID:
779442BED2A1684DBCCC8680DDDF5AA9  
Command Line:
PatchStore -store CHBTEST -patchrunid 2010.07.28.09.56.14.236 -userName Administrator -noversioncheck -unzipDirectory C:\Program Files\Click Commerce\Extranet\Temp\kiad4mv2.gyy


PatchHistory.entity.xml from the Patch.ZIP



-
-