Windows 与 .net

原文地址：https://msdn.microsoft.com/en-us/library/bb822049(v=vs.110).aspx

NET Framework Versions and Dependencies

.NET Framework (current version)

Other Versions

Each version of the .NET Framework contains the common language runtime (CLR), the base class libraries, and other managed libraries. This topic describes the key features of the .NET Framework by version, provides information about the underlying CLR versions and associated development environments, and identifies the versions that are installed by the Windows operating system.

Note

For information on downloading and installing the .NET Framework, see Installing the .NET Framework.

The following table summarizes .NET Framework version history and correlates each version with Visual Studio, Windows, and Windows Server. Note that Visual Studio provides multi-targeting, so you are not limited to the version of the .NET Framework that is listed.

Each new version of the .NET Framework retains features from the previous versions and adds new features. The CLR is identified by its own version number. The .NET Framework version number is incremented at each release, although the CLR version is not always incremented. For example, the .NET Framework 4, 4.5, and later releases include CLR 4, but the .NET Framework 2.0, 3.0, and 3.5 include CLR 2.0. (There was no version 3 of the CLR.)

See .NET Framework System Requirements for a complete list of supported operating systems. For downloads, see the installation guide. For determining which version(s) of the .NET Framework is installed on a computer, see How to: Determine Which .NET Framework Versions Are Installed.

In the table, the versions marked with * must be enabled in Control Panel (for Windows) or enabled through the Server Manager (for Windows Server).

.NET Framework version

CLR version

Features

Included in Visual Studio version

? Included in
+ Can be installed on
Windows

? Included in
+ Can be installed on
Windows Server

To determine installed .NET version

Net 4.6.1

4

  • Support for X509 certificates containing ECDSA

  • Always Encrypted support for hardware protected keys in ADO.NET
  • Spell checking improvements in WPF
  • More...

? 10 November Update

+ 10
+ 8.1
+ 8
+ 7

+ 2012 R2
+ 2012
+ 2008 R2 SP1
+ 2008 SP2

Use ReleaseDWORD:

  • 394254 (Windows 10 November Update)

  • 394271 (all other OS versions)

(seeinstructions)

.NET 4.6

4

  • Compilation using .NET Native

  • ASP.NET Core 5
  • Event tracing improvements
  • Support for page encodings
  • More...

2015, although some .NET libraries are available on NuGet. For more information see, The .NET Framework and Out-of-Band Releases.

? 10
+ 8.1
+ 8
+ 7
+ Vista

+ 2012 R2
+ 2012
+ 2008 R2 SP1
+ 2008 SP2

Use ReleaseDWORD:

  • 393295 (Windows 10)

  • 393297 (all other OS versions)

(seeinstructions)

4.5.2

4

  • New APIs for transactional systems and ASP.NET

  • System DPI resizing in Windows Forms controls
  • Profiling improvements
  • ETW and stress logging improvements
  • More...

-

+ 8.1
+ 8
+ 7
+ Vista

+ 2012 R2
+ 2012
+ 2008 R2 SP1
+ 2008 SP2

Use ReleaseDWORD: 379893
(seeinstructions)

4.5.1

4

  • Support for Windows Phone Store apps

  • Automatic binding redirection
  • Performance and debugging improvements
  • More...

2013

? 8.1
+ 8
+ 7
+ Vista

? 2012 R2
+ 2012
+ 2008 R2 SP1
+ 2008 SP2

Use ReleaseDWORD:

  • 378675 (Windows 8.1)

  • 378758 (all other)

(seeinstructions)

4.5

4

  • Support for Windows Store apps

  • WPF, WCF, WF, ASP.NET updates
  • More...

2012

? 8
+ 7
+ Vista

? 2012
+ 2008 R2 SP1
+ 2008 SP2

Use ReleaseDWORD: 378389
(seeinstructions)

4

4

  • Expanded base class libraries

  • Cross-platform development with Portable Class Library
  • MEF, DLR, code contracts
  • More...

2010

+ 7
+ Vista

+ 2008 R2 SP1
+ 2008 SP2
+ 2003

Seeinstructions

3.5

2.0

  • AJAX-enabled websites

  • LINQ
  • Dynamic data
  • More...

2008

? 10? 8.1*
? 8*
? 7
+ Vista

?2008 R2 SP1*
+ 2012 R2
+ 2012
+ 2008 SP2
+ 2003

Seeinstructions

3.0

2.0

  • WPF, WCF, WF, CardSpace

-

? Vista

? 2008 R2 SP1*
? 2008 SP2*
+ 2003

Seeinstructions

2.0

2.0

  • Generics

  • ASP.NET additions
  • More...

2005

-

? 2008 R2 SP1
? 2008 SP2
? 2003

Seeinstructions

1.1

1.1

  • ASP.NET and ADO.NET updates

  • Side-by-side execution
  • More...

2003

-

? 2003

Seeinstructions

1.0

1.0

First version of the .NET Framework.

Visual Studio .NET

-

-

Seeinstructions

In general, you should not uninstall any versions of the .NET Framework that are installed on your computer, because an application you use may depend on a specific version and may break if that version is removed. You can load multiple versions of the .NET Framework on a single computer at the same time. This means that you can install the .NET Framework without having uninstall previous versions. For more information, see Getting Started with the .NET Framework.

Targeting and Running .NET Framework apps for version 4.5 and later

The .NET Framework 4.5 is an in-place update that replaces the .NET Framework 4 on your computer, and similarly, the .NET Framework 4.5.1 4.5.2, and 4.6 are in-place updates to the .NET Framework 4.5, which means that they use the same runtime version, but the assembly versions are updated and include new types and members. After you install one of these updates, your .NET Framework 4 or .NET Framework 4.5 apps should continue to run without requiring recompilation. However, the reverse is not true. We do not recommend running apps that target a later version of the .NET Framework on the .NET Framework 4.5. The following guidelines apply:

  • In Visual Studio 2013, you can choose the .NET Framework 4.5 as the target framework for a project (this sets the GetReferenceAssemblyPaths.TargetFrameworkMoniker property) to compile the project as a .NET Framework 4.5 assembly or executable. This assembly or executable can then be used on any computer that has the .NET Framework 4.5, 4.5.1, 4.5.2, or 4.6 installed.

  • In Visual Studio, you can choose the .NET Framework 4.5.1 as the target framework for a project (this sets theGetReferenceAssemblyPaths.TargetFrameworkMoniker property) to compile the project as a .NET Framework 4.5.1 assembly or executable. This assembly or executable should be run only on computers that have the .NET Framework 4.5.1 installed. An executable that targets the .NET Framework 4.5.1 will be blocked from running on a computer that only has the .NET Framework 4.5 installed, and the user will be prompted to install the .NET Framework 4.5.1. In addition, .NET Framework 4.5.1 assemblies should not be called from a .NET Framework 4.5 app.

Some changes in the .NET Framework may require changes to your app code; see App Compatibility in the .NET Framework 4.5 before you run your existing apps with the .NET Framework 4.5 or later versions. For more information about installing the current version, see Installing the .NET Framework. For information about support for the .NET Framework, see Microsoft .NET Framework Support Lifecycle Policy on the Microsoft Support website.

Targeting and running apps for older versions

The .NET Framework versions 2.0, 3.0, and 3.5 are built with the same version of the CLR (CLR 2.0). These versions represent successive layers of a single installation. Each version is built incrementally on top of the earlier versions. It is not possible to run versions 2.0, 3.0, and 3.5 side by side on a computer. When you install version 3.5, you get the 2.0 and 3.0 layers automatically, and apps that were built for versions 2.0, 3.0, and 3.5 can all run on version 3.5. However, the .NET Framework 4 ends this layering approach. Starting with the .NET Framework 4, you can use in-process side-by-side hosting to run multiple versions of the CLR in a single process. For more information, seeAssemblies and Side-by-Side Execution.

In addition, if your app targets version 2.0, 3.0, or 3.5, your users may be required to enable the .NET Framework 3.5 on a Windows 8 or Windows 8.1 computer before they can run your app. For more information, see Installing the .NET Framework 3.5 on Windows 8, Windows 8.1 and Windows 10.

Next steps

See Also

Version Compatibility in the .NET Framework
Microsoft .NET Framework Support Lifecycle Policy

时间： 2024-10-27 01:07:51

Windows 与 .net的相关文章

Windows API参考大全新编

书名:新编Windows API参考大全 作者:本书编写组 页数:981页 开数:16开 字数:2392千字 出版日期:2000年4月第二次印刷 出版社:电子工业出版社 书号:ISBN 7-5053-5777-8 定价:98.00元 内容简介 作为Microsoft 32位平台的应用程序编程接口,Win32 API是从事Windows应用程序开发所必备的.本书首先对Win32 API函数做完整的概述:然后收录五大类函数:窗口管理.图形设备接口.系统服务.国际特性以及网络服务:在附录部分,讲解如何

Windows Server定时重启任务制定

[本篇以Windows Server 2012 R2为例] 第一步:编写重启脚步 其实就是一句话:shutdown /r 其他shutdown命令参考可以使用shutdown /?查阅 第二步:设置任务计划程序 1.再开始-所有应用中找到任务计划程序 2.展开任务计划程序库,这里对任务计划程序做了很多的分类,我们找到System Manager类,在此类下创建自动重启系统任务 3.选择窗口右侧的创建任务(也可以使用创建基本任务,它是以向导的方法创建) 4.常规页面用于定义任务名称及执行任务的用户

windows安装TortoiseGit详细使用教程【基础篇】

环境:win8.1 64bit 安装准备: 首先你得安装windows下的git msysgit1.9.5 安装版本控制器客户端tortoisegit  tortoisegit1.8.12.0 [32和64别下载错,不习惯英文的朋友,也可以下个语言包] 一.安装图解: 先安装GIT[一路默认即可] 安装好git以后,右键,会发现菜单多了几项关于GIT的选项 2.安装tortoisegit[一路默认即可] 安装好以后,右键,会发现菜单多了几项关于tortoisegit的选项 到此,安装算完成了,相

Windows下尝试PHP7提示丢失VCRUNTIME140.DLL的问题解决

前天PHP7.0.0正式版发布了,有一些比较好的改进,官方也说速度比php5.6快了两倍,性能上有了很大提升,并且也发布了从php5.x向php7迁移的问题,所以今后php网站迁移后能够大幅度的提升网站性能,所以为了尝鲜我也去php官网下载了7.0的版本,通过命令行进行独立的测试,下载zip包后解压出来,下载后进入目录,将php.ini-development改为php.ini其余的参数暂时不用修改,然后在当前目录下新建test.php,输入简单的代码: 1 <?php 2 echo "H

AD 脚本kixtart运用之三（添加windows共享打印机）

在http://windyma.blog.51cto.com/661702/1967027文章,已做好用户脚本基础上 在脚本文件kixtart.kix里添加如下内容: --------------------------------------- IF INGROUP ("Color_Printer") If AddPrinterConnection ("\\zsprinter.nccn.int\NEO-Color-Printer") = 0 ? "Add

Install Hyper-V on Windows 10

? Enable Hyper-V to create virtual machines on Windows 10.Hyper-V can be enabled in many ways including using the Windows 10 control panel, PowerShell (my favorite) or using the Deployment Imaging Servicing and Management tool (DISM). This documents

Windows Git+TortoiseGit简易使用教程

转载自 http://blog.csdn.net/jarelzhou/article/details/8256139 官方教程:http://tortoisegit.org/docs/tortoisegit/(英文版) 为什么选择Git 效率 很多人有一种习惯吧,什么软件都要最新的,最好的.其实吧,软件就是工具,生产力工具,为的是提高我们的生产力.如果现有的工具已经可以满足生产力要求了,就没有必要换了.生产效率高低应当是选择工具的第一位. 历史 开源世界的版本控制系统,经历了这么几代: 第一代,

在原生Windows安装Keras

既然要深入学习,就不能和时代脱节,所以选择了keras,资源相对比较丰富.由于Windows饱受歧视,各种文档都不推荐使用.但我又没有换系统的成本,所以还是凑合下,毕竟他们给出了方法,稍微折腾一下还是可以的.参考整合了链接[1-2]的tensorflow安装教程和链接[4]的keras安装教程,感谢原作者! 一.python. 单纯的肯定不方便:所以先装上anaconda.集成度很高,非常给力,不然各种scipy啥的会搞得很麻烦.注意版本的选择,python 3.5~3.6可以,因为tensor

Windows Server 2012配置L2TP服务环境

在上一篇文章<Windows Server 2012配置VPN服务环境>中讲解了在Windows Server2012环境中的基础VPN搭建,但是只能支持PPTP的VPN连接.这篇文章进一步完善了VPN基于L2TP的连接讲解. 在百度上也没有找到一个Windows2012 很全的L2TP服务搭建的方案,所以自己编辑了一个给有需要的朋友们参考. 准备环境:Windows Server 2012R2 数据中心版64位,基础的VPN服务环境已经搭建完成. 功能需求:完善VPN服务器来支持L2TP类型

VmWare平台Windows Server 2012 无响应宕机

我们生产服务器都部署在VMware ESXi 5.5平台上,最近大半年的时间,偶尔就会出现操作系统为Windows Servre 2012的服务器出现没有任何响应(unresponsive)的情况,出现问题的时候,服务器有下面一些现象: 1: 应用程序无法访问SQL Server数据库,使用Microsoft SQL Server Management Sutdio去测试连接数据库,也会返回连接错误. 2: 网络有时候能Ping通,有时候是Ping不通的情况. 3: 远程连接无法访问服务器,从V