I always install over the previous Clarion version. At times, I have had to rely on uninstall, but it has proven to be reliable. I have many ABC class and template “customizations”, but these generally are not affected by a new version. If it is known or appears there are changes in the shipping classes or templates, I rely upon Beyond Compare to help get it sorted. It would be very helpful, of course, if SV gave users an install option for classes & templates when changes have been made. However, I certainly won’t hold my breath for that user friendliness to happen.
I install over my current X:\Clarion11 but I keep a backup. I also install a “Clean” version with no changes so I have just what SV shipped for every release.
E.g. if X:\Clarion11 in my 11.0.13401 and I am installing 13505
Copy X:\Clarion11 to X:\Clarion11.13401_Carl to save my 13401
Delete the BACKUP folder in X:\Clarion11 or it just grows.
Rename X:\Clarion11 to X:\Clarion11_HIDE_Carl so I can install Clean
MkDir X:\Clarion11 an empty folder for clean
Install 13505 to X:\Clarion11
Rename X:\Clarion11 as X:\Clarion11.13505_Clean
Rename X:\Clarion11_HIDE_Carl back to X:\Clarion11 so I have my custom version
Install 13505 to X:\Clarion11 so my Custom version is updated
Run Clarion and register the tremplates
Now I can compare files the new 13505_Clean to my previously saved in 13401_Clean to see only what SV changed
Then I compare X:\Clarion11 to my X:\Clarion11.13401_Carl version to see how my install changed
I modify the shipping Templates and LibSrc
I can reverse back to prior versions by renaming folders.
I think on ClarionMag Dave Harms has an article on how he deals with new releases.
I never install into an old version’s folder.
If I’m installing an update to the current version, I rename the folder to \Clarion11.1.12345 then install to \Clarion11.1. Then I usually use Beyond Compare to copy over the Accessories stuff, unless the accessories need to be recompiled by the vendor.