|
Upgrading SlickEdit® 2008 |
|
|
We recommend keeping up with SlickEdit releases and updates to get the latest features and bug fixes. Major versions contain many new features and enhancements to SlickEdit. Minor versions are usually released subsequently to a major version and contain additional enhancements. Hot fixes are published frequently and contain a smaller set of changes to address a specific problem with the previous release.
SlickEdit automatically checks and notifies you when a new major or minor version is available. When an update is available, the Update Manager displays a dialog showing a list of available updates and descriptions, and provides a link to download the update.
You can set the frequency of how often SlickEdit checks for these updates and change proxy settings through the Update Manager Options dialog. To access these options, from the SlickEdit main menu, click Help > Product Updates > Options (or click the Options button on the Update Manager dialog).
You can also check for updates manually. From the SlickEdit main menu, click Help > Product Updates > New Updates. Or, visit the Support Web site at www.slickedit.com/support and click Updates.
SlickEdit creates a versioned subdirectory in your configuration directory corresponding to each version of SlickEdit you have installed. SlickEdit migrates your settings to a new subdirectory corresponding to the new version the first time the new version is run. However, as a precaution, we recommend that prior to installing an update, exit SlickEdit and make a backup of your user configuration directory.
Certain customizations that you have made to the editor are not preserved. These are:
• Modifications to menus and toolbars
• Custom forms
If you have added your own toolbar, you can reload the macros that contain these customizations. Most of these changes are saved in vusrobjs.e (Windows) or vunxobjs.e (UNIX/Linux/Mac). To reload these macros, first, copy the vusrobjs.e or vunxobjs.e file from the previous configuration directory to your new configuration directory. Then, to load these files, simply activate the SlickEdit command line (by pressing Esc in most emulations) and enter the file’s full path and file name. If the path contains spaces, be sure to surround it with double quotes.
| NOTE All customizations or additions to the main SlickEdit toolbar (known as the Standard toolbar) are lost after an upgrade, because SlickEdit rebuilds the toolbar for each new version. |
You can continue to run a previous version of SlickEdit by installing the new version into a new directory. Because the config directories are versioned, each version of SlickEdit will locate the matching settings.
Hot fixes are small, localized changes to address a specific problem with the previous release. They can consist of Slick-C® modules, configuration files, installation files, or DLL files. Hot fixes are distributed as ZIP files and made available on the SlickEdit Support Web site at www.slickedit.com/support. For convenience, a number of hot fixes may be aggregated into a single ZIP file.
| NOTE If a user loads a hot fix on a multi-user installation of SlickEdit, only that user will be updated. |
To install a hot fix, complete the following steps:
1. Save the ZIP file to any location on your computer.
2. From the SlickEdit menu, click Help > Product Updates > Load Hot Fix (or use the command load_hotfix). The Apply Hot Fix dialog appears.
3. Browse to and select the hot fix ZIP file, then click OK.
4. A confirmation prompt appears describing the hot fix. Click Yes. The installation starts.
Details about the installed fix will be sent to the Output tool window.
To see the list of hot fixes installed, from the SlickEdit menu, click Help > Product Updates > List Installed Fixes (or use the command list_hotfixes). A summary sheet appears with the location of the hot fix ZIP file, its revision number, the date it was published, and its description.
To unload a hot fix, use the unload_hotfix command from the SlickEdit command line. At the prompt, select the hot fix to unload and click OK.
| NOTE Unloading a hot fix will reload the original files distributed with the previously installed release of SlickEdit. If other hot fixes include the same file or are dependent on the unloaded files, SlickEdit may behave unpredictably. If more than one hot fix has been installed, you may need to reinstall the other hot fixes after removing one of them. |
< Back to SlickEdit Documentation
< Back to Product Documentation
|
