When do I need to upgrade my Code Protector Version and what are the implications of such an upgrade?
Whenever new SVM/Runtime functionality is released you will need to upgrade your Code Protector to take advantage of the new functionality.
You do not normally have to upgrade Code Protector to take advantage of upgrades to the SLP Online service i.e. it is possible to continue to use existing versions of Code Protector against newer versions of the SLP Online Service.
New Runtime functionality:
If you want to avail of SVM/Runtime features added after the point when your permutation was generated or last updated then you first need to either generate a new Permutation or update an existing one on SLP Online service. The resulting Permutation includes the code updates representing the SVM/Runtime enhancements, which can then be downloaded to be used with Code Protector.
The version number of the SLP Code Protector you use must be identical to the version number of your Permutation. In other words, a version 3 Code Protector requires a version 3 Permutation. Therefore to use an updated SLP Permutation, an existing Code Protector will need to be updated to the same version as the Permutation.
If you switch to a newer version of Code Protector, you will need to update your Permutation(s) on the SLP Online Service (see How To Update Permutations). Note that updating a permutation on the server is not a reversible process - Permutations created or updated on the SLP Online Service at any point in time always contain the most recent version of the SVM/runtime and are only usable with a Code Protector of the same version.
New Code Protector Functionality
It is possible that an update of Code Protector contains new functionality not related to SVM/Runtime upgrades e.g., GUI enhancements. This is rarely the case. Where this occurs, the accompanying instructions would detail any need to update one's SVM/Runtime at the same time.
Unless one is informed to the contrary by InishTech, upgrading of Code Protector does not have to be done immediately. If you do not wish to avail of new SVM/Runtime functionality then you can continue to transparently use your existing Code Protector/Permutation combination against the updated SLP Online Service.
It is also possible to use several Code Protector versions against a single SLP Online account e.g. one Code Protector/Permutation combination for an existing product and another Code Protector/Permutation versions for a separate new product e.g. VSTO application. (As the Code Protector SDK installs into a fixed directory in order to avoid the confusion that would result from side-by-side installation of multiple Code Protectors, one can only have a single specific version installed per machine at any time, i.e., it's ordinarily the case that a build agent machine or a single developer's machine will only have one Code Protector with the Permutation(s) in sync with that version.)
There is no requirement that all SVM/Runtimes or Code Protectors using a SLP Online Server account have are the same version as each other or as the most recently updated version of one's permutation stored on the SLP Online Service. Also, if you do upgrade your Code Protector/Permutation combination you will NOT need to reissue licenses to your existing customers who receive new distributions protected using a newer Code Protector; you only need to issue new licenses if you have created new products or SKUs e.g. should you decide to make a 64 bit version of your product a separate SKU.