Considerations for concurrent installation of Visual Studio systems

Sometimes, for system compatibility, developers may install various versions of visual on the operating system. such as Visual2008 and 2005. Why would a developer need that? The original developer developed an ERP system in 2005 environments. Now developers think that the 2008 development platform is more suitable for themselves, you need to migrate the software to 2008 of the development environment. Because different versions feature differently, you need to use two different versions of the development environment to help test system compatibility. You need to deploy multiple versions of the development environment on the same computer at the same time. The use of professional terminology means that visual parallel installation. In this article, the author on this issue, I hope to help you readers.

Note One: Parallel installation does not support unlimited levels.

Some application systems have conflicting versions. such as Jinshan poison PA, in the installation of a new version of antivirus software, the system will be the original version of the test. If an older version is found, the user is reminded to delete the original version or to upgrade on the original version. In short, can not be on the same computer with a number of different versions of Jinshan poison PA software.

This limitation is not true for the Visual Studio development platform. That is, Visual Studio supports parallel installations, and several different versions of the Visual Studio development platform can be located on a single host. It is also limited, and not all versions of Visual Studio can be installed on the same operating system. In practical work, there is no need for this. For Visual Studio2008, it allows 2002, 2003, 2005, and 2008 to be installed on the same host at the same time. Again in the version, will not be able to coexist with the 2008.

Note Two: The interaction between versions.

Sometimes developers may personalize settings and adjustments for a version of Visual Studio. So does this change to a particular version affect the functionality of other versions? This is also the place to pay special attention to in practical work. The first thing to be sure is that they are willing to have an impact. Because some of the content they have a connection to each other. As a developer, this problem cannot be avoided if there is a need for parallel installation. The author has made some summary to the mutual influence factor, for everybody's reference.

First effect: Remove the impact of a version of Visual Studio on other versions. When the application software is upgraded, developers feel that the original version is not needed and may be uninstalled. Does the uninstall operation adversely affect other existing versions of the system? Typically, the remaining versions of Visual Studio are still available after you delete a version. However, if you uninstall any version on a host that installs multiple versions of Visual Studio, the system deletes file associations for all existing versions of the development environment. This means that the user cannot open a file by double-clicking the Visual Studio application file directly. Instead, you can open visual Studio First, and then open it by using the file and opening features. Obviously this will increase the complexity of the operation. When this happens, how to solve it? A simple fix is provided in Visual Studio2008. In the toolbar, you can select the options, Environment, General button, and then in the Open dialog box, select the Restore file association feature. After this operation is replaced, the system will automatically establish an association between the files in the operating system and Visual Studio.