当前位置: 首页 > 微软应用 > 系统工具 > 正文
.NET 框架 Microsoft .NET Framework 4.7.1 中文离线安装包正式发布

.NET 框架 Microsoft .NET Framework 4.7.1 中文离线安装包正式发布

作者:大眼仔~旭 日期:2个月前 (10-17) 围观:57263+ 评论:7 条

摘要:Microsoft .NET Framework 4.7.1 中文离线安装版 中文离线安装包 系统必备由大眼仔旭(www.dayanzai.me)发布。微软昨晚发布了 Visual Studio 2017、.NET Framework 4.7 正式版,面向 Windows 10 的全新开发环境就此成型。Visual S…

Microsoft .NET Framework 4.7.1 中文离线安装版 中文离线安装包 系统必备由大眼仔旭(www.dayanzai.me)发布。微软昨晚发布了 Visual Studio 2017、.NET Framework 4.7 正式版,面向 Windows 10 的全新开发环境就此成型。Visual Studio 2017 的各个版本已经开放下载和订阅,.NET Framework 4.7 也来了。 .NET Framework 4.7 又被称为 .NET 2017,将会集成在 Windows 10 之中,同时支持 32/64 位的 Windows Vista SP2、Windows 7 SP1、Windows 8、Windows 8.1、Windows Server 2008 SP2、Windows Server 2008 R2 SP1、Windows Server 2012、Windows Server 2012 R2,支持简体中文等多种语言。

它在 4.5.1 的基础上新增了大量改进,涉及 WPF、WCF、Windows Workflow、高 DPI Windows Forms、RyuJIT 即时编译器、SIMD 指令集、垃圾收集器、ADO.NET、网络、兼容性等各个方面,还大幅提升了 .NET 应用程序的运行速度。

开发人员可以点此了解详细情况。普通用户只管安装就是了,说不定今后哪个程序或组件就需要它才能运行。

.NET框架(.NET Framework) 是由微软开发,一个致力于敏捷软件开发(Agile softwaredevelopment)、快速应用开发(Rapidapplication development)、平台无关性和网络透明化的软件开发平台。.NET是微软为下一个十年对服务器和桌面型软件工程迈出的第一步。.NET包含许多有助于互联网和内部网应用迅捷开发的技术。

Microsoft .NET Framework 4.6.2 中文离线安装包

Microsoft .NET Framework 4.6.2 中文离线安装包

.NET框架是一个多语言组件开发和执行环境,它提供了一个跨语言的统一编程环境。.NET框架的目的是便于开发人员更容易地建立Web应用程序和Web服务,使得Internet上的各应用程序之间,可以使用Web服务进行沟通。从层次结构来看,.NET框架又包括三个主要组成部分:公共语言运行时(CLR:Common Language Runtime)、服务框架(Services Framework)和上层的两类应用模板——传统的Windows应用程序模板(Win Forms)和基于ASP NET的面向Web的网络应用程序模板(Web Forms和Web Services)。

公共语言运行时(CLR),是一个运行时环境,管理代码的执行并使开发过程变得更加简单。CLR是一种受控的执行环境,其功能通过编译器与其它工具共同展现。

在CLR之上的是服务框架,它提供了一套开发人员希望在标准语言库中存在的基类库,包括集合、输入/输出、字符串及数据类。

那么,在Windows DNA(分布式集成网络应用体系结构)之后,微软提出新的.NET框架(新托管代码编程模型)的主要原因是什么?

问题出现在已开发了多种技术的整合的一个单一应用程序的子系统上。例如,一个制造企业有不同的系统,如库存管理系统,物料清单系统,财务总帐系统,所有使用可用于应用程序开发的各种技术实现的。这些系统需要集成在一起,从而形成一个更高级别的企业信息系统的组织。要做到这一点,应用程序开发人员必须使用如微 软的分布式组件对象模型(DCOM),通用对象请求代理体系结构(CORBA),Java远程方法调用(RMI)等技术。然而,这些分布的技术通过已开发的应用程序编程语言非常紧密地耦合在一起。

跨语言的互操作性也是受限的。例如,如果在Visual C++类已经被创建,那么不可能在Visual Basic开发新的类并将其扩展到Visual C++。因此,开发者将不得不用每一种项目中用到的语言重新编写同样的逻辑的类。功能的可重用性得到了支持,但在早期的技术,真正的代码的可重用性是不可用。因此,开发人员不得不学习被用于应用程序的开发组织用到的所有语言。注册的COM组件。COM组件注册,才可以在目标机器上使用的应用程序。应用程序必须查找Windows注册表中查找并加载的COM组件。

Microsoft .NET Framework 4.6.2 中文离线安装包

Microsoft .NET Framework 4.6.2 中文离线安装包

这是脱机安装程序。为 Web 和脱机安装方式提供不同的安装程序。如希望在安装过程中为自己的产品或应用程序重新分配这两个安装程序中的一个,我们建议选择 Web 安装程序,因为它比较小且通常下载速度比较快。您可以在此处下载 Web 安装程序。

Microsoft 建议您尽可能使用 Web 安装程序代替脱机程序包,以获得最佳的效率并满足带宽要求。

脱机程序包可在由于没有 Internet 连接导致 Web 安装程序无法使用的情况下使用。该程序包比 Web 安装程序包大,且不包含语言包。您可以从此处下载并安装语言包。

虽然 .NET Framework 的此版本与 .NET Framework 3.5 SP1 和更低版本一起运行,但它对 .NET Framework 4 和 .NET Framework 4.5 执行就地更新。

支持的操作系统
Windows 7 Service Pack 1, Windows 8, Windows Server 2008 R2 SP1, Windows Server 2008 Service Pack 2, Windows Server 2012, Windows Vista Service Pack 2
硬件要求:
1 GHz 或更快的处理器
512 MB RAM
850 MB 的可用硬盘空间 (x86)
2 GB 的可用硬盘空间 (x64)

官方主页

Microsoft .NET Framework 4.7.1 更新日志
Core
Support for .NET Standard 2.0
.NET Standard defines a set of APIs that must be available on each .NET implementation that supports that version of the standard. The .NET Framework 4.7.1 fully supports .NET Standard 2.0 and adds about 200 APIs that are defined in .NET Standard 2.0 and are missing from the .NET Framework 4.6.1, 4.6.2, and 4.7. (Note that these versions of the .NET Framework support .NET Standard 2.0 only if additional .NET Standard support files are also deployed on the target system.) For more information, see “BCL – .NET Standard 2.0 Support” in the .NET Framework 4.7.1 Runtime and Compiler Features blog post.

Support for configuration builders
Configuration builders allow developers to inject and build configuration settings for applications dynamically at run time. Custom configuration builders can be used to modify existing data in a configuration section or to build a configuration section entirely from scratch. Without configuration builders, .config files are static, and their settings are defined some time before an application is launched.
To create a custom configuration builder, you derive your builder from the abstract ConfigurationBuilder class and override its ConfigurationBuilder.ProcessConfigurationSection and ConfigurationBuilder.ProcessRawXml. You also define your builders in your .config file. For more information, see the “Configuration Builders” section in the .NET Framework 4.7.1 ASP.NET and Configuration Features blog post.

Run-time feature detection
The System.Runtime.CompilerServices.RuntimeFeature class provides a mechanism for determine whether a predefined feature is supported on a given .NET implementation at compile time or run time. At compile time, a compiler can check whether a specified field exists to determine whether the feature is supported; if so, it can emit code that takes advantage of that feature. At run time, an application can call the RuntimeFeature.IsSupported method before emitting code at runtime. For more information, see Add helper method to describe features supported by the runtime.

Value tuple types are serializable
Starting with the .NET Framework 4.7.1, System.ValueTuple and its associated generic types are marked as Serializable, which allows binary serialization. This should make migrating Tuple types, such as Tuple<T1,T2,T3> and Tuple<T1,T2,T3,T4>, to value tuple types easier. For more information, see “Compiler — ValueTuple is Serializable” in the .NET Framework 4.7.1 Runtime and Compiler Features blog post.

Support for read-only references
The .NET Framework 4.7.1 adds the System.Runtime.CompilerServices.IsReadOnlyAttribute. This attribute is used by language compilers to mark members that have read-only ref return types or parameters. For more information, see “Compiler — Support for ReadOnlyReferences” in the .NET Framework 4.7.1 Runtime and Compiler Features blog post. For information on ref return values, see Ref return values and ref locals (C# Guide) and Ref return values (Visual Basic).

Common language runtime (CLR)
Garbage collection performance improvements
Changes to garbage collection (GC) in the .NET Framework 4.7.1 improve overall performance, especially for Large Object Heap (LOH) allocations. In the .NET Framework 4.7.1, separate locks are used for Small Object Heap (SOH) and LOH allocations, which allows LOH allocations to occur when Background GC (BGC) is sweeping the SOH. As a result, applications that make a large number of LOH allocations should see a reduction in allocation lock contention and improved performance. For more information, see the “Runtime — GC Performance Improvements” section in the .NET Framework 4.7.1 Runtime and Compiler Features blog post.

Support for portable PDBs
The .NET Framework starting with version 4.7.1 supports portable PDBs. While standard PDB files are Windows-only, portable PDB files can be created and read on all platforms. In most cases, the file format is transparent to an application running on a particular .NET implementation. An exception is an application that dynamically emits an assembly at run time; in this case, the ability to emit a portable PDB can offer a performance improvement and reduce the application’s memory footprint.
You can determine at run time whether portable PDBs are supported on the current .NET implementation by passing the string “PortablePdb” to the RuntimeFeature.IsSupported(String) method before emitting the assembly.

Networking
SHA-2 support for Message.HashAlgorithm
In the .NET Framework 4.7 and earlier versions, the Message.HashAlgorithm property supported values of HashAlgorithm.Md5 and HashAlgorithm.Sha only. Starting with the .NET Framework 4.7.1, HashAlgorithm.Sha256, HashAlgorithm.Sha384, and HashAlgorithm.Sha512 are also supported. Whether this value is actually used depends on MSMQ, since the Message instance itself does no hashing but simply passes on values to MSMQ. For more information, see the “SHA-2 support for Message.HashAlgorithm” section in the .NET Framework 4.7.1 ASP.NET and Configuration features blog post.

ASP.NET
Execution steps in ASP.NET applications
ASP.NET processes requests in a predefined pipeline that includes 23 events. ASP.NET executes each event handler as an execution step. In versions of ASP.NET up to the .NET Framework 4.7, ASP.NET can’t flow the execution context due to switching between native and managed threads. Instead, ASP.NET selectively flows only the HttpContext. Starting with the .NET Framework 4.7.1, the HttpApplication.OnExecuteRequestStep(Action<HttpContextBase,Action>) method also allows modules to restore ambient data. This feature is targeted at libraries concerned with tracing, profiling, diagnostics, or transactions, for example, that care about the execution flow of the application. For more information, see the “ASP.NET Execution Step Feature” in the .NET Framework 4.7.1 ASP.NET and Configuration Features blog post.

ASP.NET HttpCookie parsing
The .NET Framework 4.7.1 includes a new method, HttpCookie.TryParse, that provides a standardized way to create an HttpCookie object from a string and accurately assign cookie values such as expiration date and path. For more information, see “ASP.NET HttpCookie parsing” in the .NET Framework 4.7.1 ASP.NET and Configuration Features blog post.

SHA-2 hash options for ASP.NET forms authentication credentials
In the .NET Framework 4.7 and earlier versions, ASP.NET allowed developers to store user credentials with hashed passwords in configuration files using either MD5 or SHA1. Starting with the .NET Framework 4.7.1, ASP.NET also supports new secure SHA-2 hash options such as SHA256, SHA384, and SHA512. SHA1 remains the default, and a non-default hash algorithm can be defined in the web configuration file. For example:
XML

<system.web>
<authentication mode=”Forms”>
<forms loginUrl=”~/login.aspx”>
<credentials passwordFormat=”SHA512″>
<user name=”jdoe” password=”6D003E98EA1C7F04ABF8FCB375388907B7F3EE06F278DB966BE960E7CBBD103DF30CA6D61F7E7FD981B2
E4E3A64D43C836A4BEDCA165C33B163E6BCDC538A664″ />
</credentials>
</forms>
</authentication>
</system.web>

资源:NDP471-KB4033342-x86-x64-AllOS-ENU.exe
解压密码:www.dayanzai.me
转载请保留出处,谢谢合作~
点击下载

声明:大眼仔旭 | 本文采用[BY-NC-SA]协议进行授权
文章名称:《.NET 框架 Microsoft .NET Framework 4.7.1 中文离线安装包正式发布
文章固定链接:http://www.dayanzai.me/net-framework.html
除注明转载文章外 转载时必须以链接形式注明作者和原始出处及本声明
转载声明
返回顶部