Network administrators must verify that all client computers have the required system components before they install the. NET Framework. The following list is a summary of the software requirements for installing the. NET Framework 4. For a detailed description of the software and hardware requirements, see. NET Framework System Requirements. Client operating system Minimum version and other software Windows 7 Windows 7 RTMWindows Vista Windows Vista RTMWindows XPWindows XP Service Pack 3 ( SP3) Internet Explorer 6.0 SP1 Windows Installer 3.1 or later Windows Server 20 RTMWindows Server 2008 Server Core R2 SP1 Windows Server 2003 Windows Server 2003 SP2 Internet Explorer 6.0 SP1 Windows Installer 3.1 or later Windows Imaging Component Option Description Sets quiet mode./norestart Prevents the Setup program from rebooting automatically. If you use this option, the chaining application has to capture the return code and handle rebooting (see Creating a Program with Setup and Installation Parameters). /repair Triggers the repair functionality./chainingpackage Package Name Specifies the name of the package that is doing the chaining. This information is logged and stored with the SQM data for the. NET Framework installation session. If the package name includes spaces, use double quot;tion marks as delimiters; for example: /chainingpackage Chaining Product. When you have the supporting infrastructure in place, you use System Center Configuration Manager 2007 to deploy the. NET Framework redistributable package on the network. This process involves creating and defining five primary areas: collections, packages, programs, distribution points, and advertisements. Collections are groups of Configuration Manager 2007 resources, such as users, user groups, or computers, which the. NET Development software deployment targets. For more information about collections, see Collections.
A few months ago we announced the availability of the. NET Framework, a highly compatible, in-place update to the. NET 4.x family (. NET 4, 4.5, and ). The. NET Framework was released only a few short months after the release of. NET and gives you the benefits of the greater stability, reliability, security and performance without any action beyond installing the. NET update i.e., there is no need to recompile your application to get these benefits. The quick pace at which we’re evolving and shipping means the latest fixes, features, and innovations are available in the latest version and not in legacy versions. To that end, we are making it easier than ever before for customers to stay current on the. NET Framework 4.x family of products with highly compatible, in-place updates for the. NET 4.x family. We will continue to fully support. NET 4. NET 4.5. NET, and. NET until January 12, 2016, this includes security updates as well as non-security technical support and hotfixes. Beginning January 12, 2016 only. NET Framework will continue receiving technical support and security updates. There is no change to the support timelines for any other. NET Framework version, including. NET 3.5 SP1, which will continue to be supported for the duration of the operating system lifecycle. We will continue to focus on. NET and as we outlined at both Tech Ed NA and Build earlier in 2014, we are working on a significant set of technologies, features and scenarios that will be part of. NET v Next, our next major release of the. NET Framework coming in 2015. For more details on the. NET Framework support lifecycle, visit the Microsoft Support Lifecycle site. If you have any questions regarding compatibility of the. NET Framework you may want to review the. NET Application Compatibility page. Should you have any questions that remain.
Microsoft started development on the. NET Framework in the late 1990s originally under the name of Next Generation Windows Services ( NGWS). By late 2000 the first beta versions of. NET 1.0 were released.[1] The first version of. NET Framework was released on 13 February 2002, bringing managed code to Windows NT 4.0, 98, 2000, ME and XP. Since the first version, Microsoft has released nine more upgrades for. NET Framework, seven of which have been released along a new version of Visual Studio. Two of these upgrades. NET Framework 2.0 and 4.0, have upgraded Common Language Runtime ( CLR). New versions of. NET Framework replace older versions when the CLR version is the same. The. NET Framework family also includes two versions for mobile or Embedded device use. A reduced version of the framework, the. NET Compact Framework, is available on Windows CE platforms, including Windows Mobile devices such as smartphones. Additionally, the. NET Micro Framework is targeted at severely resource-constrained devices. Contents 1 Overview 2. NET Framework 1.0 3. NET Framework 1.1 4. NET Framework 2.0 5. NET Framework 3.0 6. NET Framework 3.5 6.1 Service Pack 1. NET Framework 3.5 SP1 Client Profile 7. NET Framework 4 7.1 History 7.2 Windows Server App Fabric 8. NET Framework 4.5 8.1. NET for Metro style-apps 8.2 Core Features 8.3 Managed Extensibility Framework ( MEF) 8.4 ASP. NET 8.5 Networking 8.6. NET Framework 8.7. NET Framework 9. NET Framework 4.6 9.1. NET Framework 10 References Overview[edit] Overview of. NET Framework release history[2][3] Version number CLR version Release date Development tool Included in Replaces Windows Windows Server 1.0 1.0 Visual Studio. NET[4] XP[a] N/ A N/ A 1.1 1.1 Visual Studio. NET 2003[4] N/ A 2003 1.0[5] 2.0 2.0 Visual Studio 2005[6] N/ A 2003, 2003 R2,[7] 2008 SP2, 2008 R2 SP1 N/ A 3.0 2.0.
Download Now