- Get Stackato
- Why a Private PaaS?
- Features & Benefits
- Stackato by Language
- Compare Editions
- Stackato & Cloud Foundry
- Developer Tools
- Stackato Training
- Professional Services
- Commercial Support
- Code Recipes
Kevin "kj" Woolley, February 9, 2006
Here is a quick guide to the steps to take when upgrading any ActiveState software package running on the Windows platform. Following proper upgrade procedures can keep a variety of problems from occurring -- these errors can be fairly tricky...
Here is a quick guide to the steps to take when upgrading any ActiveState software package running on the Windows platform. Following proper upgrade procedures can keep a variety of problems from occurring -- these errors can be fairly tricky to debug.
Without further ado:
- quit all running instances of the product
- uninstall the product via the Add/Remove Programs control panel
- delete all directories where the product was installed
- install the new version of the product
You should prefer MSI or executable installers to AS packages, as the AS packages offer no uninstallation options. If you have installed something from an AS package, skip the second step above and simply delete the installation directory. This may not remove all files from the system (those that have been installed in other directories) and will not remove registry entries associated with that installation.
The third step may seem redundant, but sometimes files do get left behind, and it is good practice to make sure they are gone, as these can also cause difficult-to-diagnose problems.
In general, you don't need to worry about re-installing a license unless you are upgrading to a new major version of a piece of software. For example, upgrading from Komodo 3.1 to 3.5.2 will just work -- you don't need to install anything more.
As usual, if you have any questions, let us know at support [at] activestate [dot] com.
Subscribe to ActiveState Blogs by Email
Share this post:
Category: dynamic languages