Using Multiple Versions of a PC Application
We are regularly asked about both the wisdom and practice of running multiple app versions on the same box. While this is often responded to by people with the obvious question of -Why would someone want to do this? – it is, nonetheless, a valid question. The way to maintain and regularly use multiple versions of a single PC application is somewhat involved but is presented below. Before we get into the specifics of how it is best done, let us dispense with the justification for doing it in the first place.
Running multiple versions of the same application is typically justified based simply on need. Hopefully, a detailed example should suffice. If you have a website authored with MS FrontPage and you also need the enhanced functionality of MS Office 2007, you might find yourself in need of running both MS Office 2000 and 2007 on the same box. If you add MS Office 2007 to an Office 2000 mix – running it on the same box – you may, indeed, have enhanced functionality but very definitely at the cost of a greatly complicated operating environment. Specifically, having in this case two versions of MS Office, so as to provide for the continued usage of one of its Modules – i.e. FrontPage – means that unless you alter it somewhat you will often incur major problems and unpredictable results. This specific situation calls for a reduced version of 2000 – i.e. only FrontPage – reinstalled after deleting all of 2000. Then you would have the desired operating environment without the complexities of two, competing product families that use shared DLL’s, Registry Key Codes, etc.
Here are some tips for running dual-versions. First of all, be sure that it is something that you want and need to do. In the example above – RE: FrontPage – it is clear that there are no advanced versions of FrontPage, so maintaining a website created with it may be justified. Nonetheless, you will eventually have to bite this bullet.
Assuming that you have satisfied yourself that duel-versioning is justified, your first step is to access the Vendors website and research this very subject – in specificity. You might need to write them or pose questions on focus sites.
Next, make sure that you are installing the newer version of the application on top of – i.e. after – you have installed the earlier version. Natural timing typically takes care of this.
Create a series of test projects to verify that your dual-versioning works. This is extremely critical when extended-use projects involve real world customers or projects.
Then make sure that your Windows System Registry is clean and updated. You can purchase and download a top registry software package that does this and also performs the other registry fix functions that accomplish any needed Registry Repair as a part of your newfound performance duality.
