How Silverfrost currently implements the updates to newer versions? Because how installer works is hidden under the hood - is the way how it updates closer to one click hassle-free update like all the apps on Android or Apple phone -or- it always implies oldfashioned Uninstall-Reboot-Install-Reboot process? Will the installer run over older version and the installation will automatically take care of removing older version and environment variables without reboots and problems -or- for safety we have to go through the whole multistep process with a lot of clicks and reboot?
Updates
Dan,
I take a copy of ftn95 directory ( say as FTN95_6.10) and then install the new version over the top of the existing install. Works for me and no need to re-boot. I change the names of the FTN95 directories to switch between versions of the compiler.
John
Thanks for idea, John. Let me ask you just to check if i correctly understood - what you do is just rename older version and install new? Have you checked if installer does not add one more entry in the environment variables?
Dan,
I don't rename when installing; Before installing, I take a copy of the existing FTN95 directory then rename the copy. I then overwrite the existing install with the update. This allows for retaining any changes to /INCLUDE or ftn95.cfg etc. This is the standard approach for an update install. I do not find that environment variable settings are duplicated.
Later, if I want to retest an old version of the compiler, I change names, such as: ren FTN95 FTN95_6.30 ren FTN95_6.10 FTN95
John
Got it, thanks