Visual Studio.NET Enterprise Architecture Design Edition evaluation

visual| design 1. Overview <br>
The version according to the provider claimed to be the Chinese version of RC2, but in my opinion, it should be the legendary RTM version, the reason for this conjecture is based on the following reasons: This version does not like the RC1 version has a time limit. I refer to November 2002, and I can still start normally (and then change to 2004 as normal). And in the RC version, the word "evaluating" should appear on the Eula.txt and launch screens, but this version never appears. <br>
This version of the startup screen is displayed as an enterprise-class architectural design version. But there are no Visio XP options like the BETA2 Enterprise, and although I have installed the Visio XP Chinese version, I still don't see the reverse engineering button in that version. <br>
2. Installation <br>
There are five ISO files in total, the first four are 1.iso,2.iso,3.iso,4.iso, and the last one is Wcu.iso. The installation method has a variety of:<br>
(1) made into CD-ROM installation <br>
The ISO file is carved into a CD-ROM installation without any problems (this test step was confirmed by Comrade Lenovo no error) <br>
(2) Install <br> with virtual optical drive software
The simulation of each ISO into a virtual disc, and then installed separately, the most convenient, but also the most efficient, and will not have any problems (this test step chicken test without errors, about virtual CD-ROM software and other considerations please ask chicken). <br>
(3) hard disk installation <br>
This is my model with the blue, the steps for the ISO untie, the first four ISO placed in a folder (will be prompted to duplicate the phenomenon, ignore it), and then install from the root directory. I tested this step with blue and the only thing that needs to be noted in an ISO (I don't remember the name) is that there is a file name problem, in the following directory [extract directory]\program Files\Microsoft Visual Studio. Net\vb7\vb Samples\sfl\, there is a file: CONSOLE-LOCALIZATION-SATELLITEASSEMBLIES_VBLOCALIZEDHELLOWORLD.SFL, the last d in the engraving is not added, So you need to manually add this "D" and then go on and there will be no problem. <br>
3. Uninstall <br>
Various versions of the Uninstall method I believe that we have experienced, in fact, there is no worth recounting, but I still want to be here to wordy a few words:<br>
(1) Uninstall only the visual Stuio.net and the. NET Framework, and others, like WinDOS Component update, do not move because they are public and do not have to be uninstalled at all. <br>
(2) Uninstall process it is best not to do any work, including browsing the web, such as blue comrade, because in the process of unloading browsing our dotnet era, the result of unloading three hours did not unload, and finally interrupted the restart (as overtime:)) <br>
(3) A variety of previously installed. NET version of the software, such as their own, or other people to provide, but based on other versions of the framework, to delete all, otherwise you will not be able to install the new version of the framework. <br>
4. About WCU (Windows Component Update) <br>
In fact, this time the WCU on two files available, One is the new version of the framework placed in the Wcu.iso dotnetframework, only 20 m, just download it on the other one is the Wcu.iso root directory inside the Bootstrp.msi, 200K, is the installer runtime file, copy it to your 1 to 4 of the common decompression directory under the root directory, double-click can be run (note, be sure to copy to the root directory, or you will be prompted to lack of files, because it will install the directory below the win directory of Things). After installing the two files mentioned above, you do not have to go through the long Windows Component Update, then install Visual Studio.NET, and you can now go directly to the installation. <br>
5. Namespaces <br>
Also do not know who rumors, vowed that the official version of the namespace will be changed, so that everyone panic, I guess Microsoft will not be so silly, may be the Java Camp people to send rumors. Please rest assured that there is no change (to less now seems to be). <br>
And the original program, the source code way to upgrade no problem, directly to recompile. Even the compiled files that you originally generated can run directly inside the framework (or am I mistaken?) It doesn't seem to be there. <br>
6. Questions <br>
Microsoft's. NET development binds the Visual Studio.NET and the. NET Framework too much, and each time the framework is upgraded, visual Studio.NET, it seems counterintuitive, estimates that the issue will be resolved in the official version, like JBuilder and JDK, completely isolated and unaffected. <br>
<br>
<br>