Windows2003 + IIS6 install. Net FrameWork 4.0 compatibility with earlier versions of the test

See the document said. NET4 's framework can be backwards compatible with 2.0, 3.0, 3.5 of these versions, think is a good thing, after the server will not need time-consuming and laborious installation of 2.0, 3.5 and other frameworks. It's strange, however, that the 2.0 and 3.5 frameworks are big, so why is this much smaller 4.0 running the first few versions of the program at the same time? Is it because the Win7 brought 3.5? What will happen to the win2003?

To figure this out, I re-installed a new win2003, and after the system is installed, add IIS. And hit the SP2 patch (required). At this point the system is basically bare metal, the system. NET version is 1.1.

Then start the installation. Net4.0 framework, after installation, set up two Web sites in IIS (figure I), a vs2010 created with the default ASP. NET WebApplication uses a framework version of 4.0, in order to remove the bottom of the 4.0 edge, and the other is created with vs2008 ASP. NET Web site, and a statement in which the LINQ syntax is written (querying the files in the current directory and displaying them). After you deploy the two sites, set the user's frame version to asp.net4.0 in the properties dialog's ASP. Net property page, a dialog box pops up (Figure II), which is basically a change. NETFramework version will restart the W3SVC service (since this version is no longer running in w3wp.exe), click OK, after completion, on the browser to access, can run normally (figure III).

Figure One:

Figure II:

Might

Conclusion:

The. NET FrameWork 4.0 works well for previous versions of. NET Web sites (other types of apps should also be OK), so if you are now reloading the server's system and are about to configure the operating environment, then I recommend that you just install one. Net 4.0 of the frame on the line , the other all do not install, both fast and provincial. It can ensure the normal operation of existing applications, but also allows you to have a new development environment to learn and test new technologies.

Digression: I'm going to do this: run on the Win2003 server. Net4.0 A framework is enough, and then developed using VS2010 to do development tools, new development application positioning for the 3.5 framework version, the original 2.0 and 3.5 of the application is still unchanged, 4.0 formally after the upgrade. Actually does not raise also does not matter, the running environment is unified, the development tool unifies, uses what version is just chooses the line:). It was very cool indeed.

Windows2003 + IIS6 install. Net FrameWork 4.0 compatibility with earlier versions of the test