Version leapfrogging

[PouncingPanda]

Not likely a common problem but I observed this behavior when upgrading SlickEdit.  I have a paid for version which I use (11) and I have a trial for a version which I don't use and didn't purchase (12).  When I downloaded the latest (13) it claimed to copy my info from 12, not 11.  I haven't touched 12 in many months.  To remedy possible problems caused by this I decided to backup the 13.0.0 folder and copy the 11.0.2 folder to 13.0.0 and restart SlickEdit.  Hopefully this won't hose me but I thought this scenario should be mentioned as I'm probably not the only person to leapfrog a version despite trying a previous version demo.

I have not noticed any aberrant behavior yet as a result of this migration.

[StephenW]

I think a better idea would have been to temporarily rename the 12.0.x directory to something else (eg saved_12.0.0), and then install V13.  It should migrate the V11 settings then.

[PouncingPanda]

I agree, I didn't know it would be an issue until after the install.  If I have any problems I'll do a reinstall with this strategy.  Thanks!

[ScottW, VP of Dev]

I would caution against running that way. We can't predict what will happen if SlickEdit hits old configuration data in a new directory. We use the version numbers on the directories to key any updates.

To properly migrate your settings from v11, delete the v12 config directory and the v13 config directory. Then when you launch SlickEdit, it will see the v11 directory as the most recent one and migrate your settings from there.

[PouncingPanda]

Will do, thanks.