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

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

作者:大眼仔~旭 日期:6个月前 (04-30) 围观:82202+ 评论:8 条

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

Microsoft .NET Framework 4.7.2 中文离线安装版 中文离线安装包 系统必备由大眼仔旭(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)

官方主页

What’s new in the .NET Framework 4.7.2
The .NET Framework 4.7.2 includes new features in the following areas:
Core
ASP.NET
Networking
SQL
WPF
ClickOnce
A continuing focus in the .NET Framework 4.7.2 is improved accessibility, which allows an application to provide an appropriate experience for users of Assistive Technology. For information on accessibility improvement in the .NET Framework 4.7.2, see What’s new in accessibility in the .NET Framework.
Core
The .NET Framework 4.7.2 features a large number of cryptographic enhancements, better decompression support for ZIP archives, and additional collection APIs.
New overloads of RSA.Create and DSA.Create
The DSA.Create(DSAParameters) and RSA.Create(RSAParameters) methods let you supply key parameters when instantiated a new DSA or RSA key. They allow you to replace code like the following:
C#

// Before .NET Framework 4.7.2
using (RSA rsa = RSA.Create())
{
rsa.ImportParameters(rsaParameters);
// Other code to execute using the RSA instance.
}
with code like this:
C#

// Starting with .NET Framework 4.7.2
using (RSA rsa = RSA.Create(rsaParameters))
{
// Other code to execute using the rsa instance.
}
The DSA.Create(Int32) and RSA.Create(Int32) methods let you generate new DSA or RSA keys with a specific key size. For example:
C#

using (DSA dsa = DSA.Create(2048))
{
// Other code to execute using the dsa instance.
}
Rfc2898DeriveBytes constructors accept a hash algorithm name
The Rfc2898DeriveBytes class has three new constructors with a HashAlgorithmName parameter that identifies the HMAC algorithm to use when deriving keys. Instead of using SHA-1, developers should use a SHA-2-based HMAC like SHA-256, as shown in the following example:
C#

private static byte[] DeriveKey(string password, out int iterations, out byte[] salt,
out HashAlgorithmName algorithm)
{
iterations = 100000;
algorithm = HashAlgorithmName.SHA256;

const int SaltSize = 32;
const int DerivedValueSize = 32;

using (Rfc2898DeriveBytes pbkdf2 = new Rfc2898DeriveBytes(password, SaltSize,
iterations, algorithm))
{
salt = pbkdf2.Salt;
return pbkdf2.GetBytes(DerivedValueSize);
}
}
Support for ephemeral keys
PFX import can optionally load private keys directly from memory, bypassing the hard drive. When the new X509KeyStorageFlags.EphemeralKeySet flag is specified in an X509Certificate2 constructor or one of the overloads of the X509Certificate2.Import method, the private keys will be loaded as ephemeral keys. This prevents the keys from being visible on the disk. However:
Since the keys are not persisted to disk, certificates loaded with this flag are not good candidates to add to an X509Store.
Keys loaded in this manner are almost always loaded via Windows CNG. Therefore, callers must access the private key by calling extension methods, such as cert.GetRSAPrivateKey(). The X509Certificate2.PrivateKey property does not function.
Since the legacy X509Certificate2.PrivateKey property does not work with certificates, developers should perform rigorous testing before switching to ephemeral keys.
Programmatic creation of PKCS#10 certification signing requests and X.509 public key certificates
Starting with the .NET Framework 4.7.2, workloads can generate certificate signing requests (CSRs), which allows certificate request generation to be staged into existing tooling. This is frequently useful in test scenarios.
For more information and code examples, see “Programmatic creation of PKCS#10 certification signing requests and X.509 public key certificates” in the .NET Blog.
New SignerInfo members
Starting with the .NET Framework 4.7.2, the SignerInfo class exposes more information about the signature. You can retrieve the value of the System.Security.Cryptography.Pkcs.SignerInfo.SignatureAlgorithm property to determine the signature algorithm used by the signer. SignerInfo.GetSignature can be called to get a copy of the cryptographic signature for this signer.
Leaving a wrapped stream open after CryptoStream is disposed
Starting with the .NET Framework 4.7.2, the CryptoStream class has an additional constructor that allows Dispose to not close the wrapped stream. To leave the wrapped stream open after the CryptoStream instance is disposed, call the new CryptoStream constructor as follows:
C#

var cStream = new CryptoStream(stream, transform, mode, leaveOpen: true);
Decompression changes in DeflateStream
Starting with the .NET Framework 4.7.2, the implementation of decompression operations in the DeflateStream class has changed to use native Windows APIs by default. Typically, this results in a substantial performance improvement.
Support for decompression by using Windows APIs is enabled by default for applications that target .NET Framework 4.7.2. Applications that target earlier versions of .NET Framework but are running under .NET Framework 4.7.2 can opt into this behavior by adding the following AppContext switch to the application configuration file:
XML

<AppContextSwitchOverrides value=”Switch.System.IO.Compression.DoNotUseNativeZipLibraryForDecompression=false” />
Additional collection APIs
The .NET Framework 4.7.2 adds a number of new APIs to the SortedSet<T> and HashSet<T> types. These include:
TryGetValue methods, which extend the try pattern used in other collection types to these two types. The methods are:
`public bool HashSet.TryGetValue(T equalValue, out T actualValue);
`public bool SortedSet.TryGetValue(T equalValue, out T actualValue);
Enumerable.To* extension methods, which convert a collection to a HashSet<T>:
public static HashSet ToHashSet(this IEnumerable source);
public static HashSet ToHashSet(this IEnumerable source, IEqualityComparer comparer);
New HashSet<T> constructors that let you set the collection’s capacity, which yields a performance benefit when you know the size of the HashSet<T> in advance:
public HashSet(int capacity)
public HashSet(int capacity, IEqualityComparer comparer)
The ConcurrentDictionary<TKey,TValue> class includes new overloads of the AddOrUpdate and GetOrAdd methods to retrieve a value from the dictionary or to add it if it is not found, and to add a value to the dictionary or to update it if it already exists.
C#

public TValue AddOrUpdate<TArg>(TKey key, Func<TKey, TArg, TValue> addValueFactory, Func<TKey, TValue, TArg, TValue> updateValueFactory, TArg factoryArgument)

public TValue GetOrAdd<TArg>(TKey key, Func<TKey, TArg, TValue> valueFactory, TArg factoryArgument)
ASP.NET
Support for dependency injection in Web Forms
Dependency injection (DI) decouples objects and their dependencies so that an object’s code no longer needs to be changed just because a dependency has changed. When developing ASP.NET applications that target the .NET Framework 4.7.2, you can:
Use setter-based, interface-based, and constructor-based injection in handlers and modules, Page instances, and user controls of ASP.NET web application projects.
Use setter-based and interface-based injection in handlers and modules, Page instances, and user controls of ASP.NET web site projects.
Plug in different dependency injection frameworks.
Support for same-site cookies
SameSite prevents a browser from sending a cookie along with a cross-site request. The .NET Framework 4.7.2 adds a HttpCookie.SameSite property whose value is a System.Web.SameSiteMode enumeration member. If its value is SameSiteMode.Strict or SameSiteMode.Lax, ASP.NET adds the SameSite attribute to the set-cookie header. SameSite support applies to HttpCookie objects, as well as to FormsAuthentication and System.Web.SessionState cookies.
You can set SameSite for an HttpCookie object as follows:
C#

var c = new HttpCookie(“secureCookie”, “same origin”);
c.SameSite = SameSiteMode.Lax;
You can also configure SameSite cookies at the application level by modifying the web.config file:
XML
<system.web>
<httpCookies sameSite=”Strict” />
</system.web>
You can add SameSite for FormsAuthentication and System.Web.SessionState cookies by modifying the web config file:
XML
<system.web>
<authentication mode=”Forms”>
<forms cookieSameSite=”Lax”>
<!– … –>
</forms>
<authentication />
<sessionSate cookieSameSite=”Lax”></sessionState>
</system.web>
Networking
Implementation of HttpClientHandler properties
The .NET Framework 4.7.1 added eight properties to the System.Net.Http.HttpClientHandler class. However, two threw a PlatformNotSupportedException. The .NET Framework 4.7.2 now provides an implementation for these properties. The properties are:
CheckCertificateRevocationList
SslProtocols
SQLClient
Support for Azure Active Directory Universal Authentication and Multi-Factor authentication
Growing compliance and security demands require that many customers use multi-factor authentication (MFA). In addition, current best practices discourage including user passwords directly in connection strings. To support these changes, the .NET Framework 4.7.2 extends SQLClient connection strings by adding a new value, “Active Directory Interactive”, for the existing “Authentication” keyword to support MFA and Azure AD Authentication. The new interactive method supports native and federated Azure AD users as well as Azure AD guest users. When this method is used, the MFA authentication imposed by Azure AD is supported for SQL databases. In addition, the authentication process requests a user password to adhere to security best practices.
In previous versions of the .NET Framework, SQL connectivity supported only the SqlAuthenticationMethod.ActiveDirectoryPassword and SqlAuthenticationMethod.ActiveDirectoryIntegrated options. Both of these are part of the non-interactive ADAL protocol, which does not support MFA. With the new SqlAuthenticationMethod.ActiveDirectoryInteractive option, SQL connectivity supports MFA as well as existing authentication methods (password and integrated authentication), which allows users to enter user passwords interactively without persisting passwords in the connection string.
For more information and an example, see “SQL — Azure AD Universal and Multi-factor Authentication Support” in the .NET Blog.
Support for Always Encrypted version 2
NET Framework 4.7.2 adds supports for enclave-based Always Encrypted. The original version of Always Encrypted is a client-side encryption technology in which encryption keys never leave the client. In enclave-based Always Encrypted, the client can optionally send the encryption keys to a secure enclave, which is a secure computational entity that can be considered part of SQL Server but that SQL Server code cannot tamper with. To support enclave-based Always Encrypted, the .NET Framework 4.7.2 adds the following types and members to the System.Data.SqlClient namespace:
SqlConnectionStringBuilder.EnclaveAttestationUrl, which specifies the Uri for enclave-based Always Encrypted.
SqlColumnEncryptionEnclaveProvider, which is an abstract class from which all enclave providers are derived.
SqlEnclaveSession, which encapsulates the state for a given enclave session.
SqlEnclaveAttestationParameters, which provides the attestation parameters used by SQL Server to get information required to execute a particular Attestation Protocol.
The application configuration file then specifies a concrete implementation of the abstract System.Data.SqlClient.SqlColumnEncryptionEnclaveProvider class that provides the functionality for the enclave provider. For example:
XML
<configuration>
<configSections>
<section name=”SqlColumnEncryptionEnclaveProviders” type=”System.Data.SqlClient.SqlColumnEncryptionEnclaveProviderConfigurationSection,System.Data,Version=4.0.0.0,Culture=neutral,PublicKeyToken=b77a5c561934e089″/>
</configSections>
<SqlColumnEncryptionEnclaveProviders>
<providers>
<add name=”Azure” type=”Microsoft.SqlServer.Management.AlwaysEncrypted.AzureEnclaveProvider,MyApp”/>
<add name=”HGS” type=”Microsoft.SqlServer.Management.AlwaysEncrypted.HGSEnclaveProvider,MyApp” />
</providers>
</SqlColumnEncryptionEnclaveProviders >
</configuration>
The basic flow of enclave-based Always Encrypted is:
The user creates an AlwaysEncrypted connection to SQL Server that supported enclave-based Always Encrypted. The driver contacts the attestation service to ensure that it is connecting to right enclave.
Once the enclave has been attested, the driver establishes a secure channel with the secure enclave hosted on SQL Server.
The driver shares encryption keys authorized by the client with the secure enclave for the duration of the SQL connection.
Windows Presentation Foundation
Finding ResourceDictionaries by Source
Starting with the .NET Framework 4.7.2, a diagnostic assistant can locate the ResourceDictionaries that have been created from a given source Uri. (This feature is for use by diagnostic assistants, not by production applications.) A diagnostic assistant such as Visual Studio’s “Edit-and-Continue” facility lets its user edit a ResourceDictionary with the intent that the changes be applied to the running application. One step in achieving this is finding all the ResourceDictionaries that the running application has created from the dictionary that’s being edited. For example, an application can declare a ResourceDictionary whose content is copied from a given source URI:
XML
<ResourceDictionary Source=”MyRD.xaml”>
A diagnostic assistant that edits the original markup in MyRD.xaml can use the new feature to locate the dictionary. The feature is implemented by a new static method, ResourceDictionaryDiagnostics.GetResourceDictionariesForSource. The diagnostic assistant calls the new method using an absolute Uri that identifies the original markup, as illustrated by the following code:
C#
IEnumerable<ResourceDictionary> dictionaries = ResourceDictionaryDiagnostics.GetResourceDictionariesForSource(new Uri(“pack://application:,,,/MyApp;component/MyRD.xaml”));
The method returns an empty enumerable unless VisualDiagnostics is enabled and the ENABLE_XAML_DIAGNOSTICS_SOURCE_INFO environment variable is set.
Finding ResourceDictionary owners
Starting with the .NET Framework 4.7.2, a diagnostic assistant can locate the owners of a given ResourceDictionary. (The feature is for use by diagnostic assistants and not by production applications.) Whenever a change is made to a ResourceDictionary, WPF automatically finds all DynamicResource references that might be affected by the change.
A diagnostic assistant such as Visual Studio’s “Edit-and-Continue” facility may want extend this to handle StaticResource references. The first step in this process is to find the owners of the dictionary; that is, to find all the objects whose Resources property refers to the dictionary (either directly, or indirectly via the ResourceDictionary.MergedDictionaries property). Three new static methods implemented on the System.Windows.Diagnostics.ResourceDictionaryDiagnostics class, one for each of the base types that has a Resources property, support this step:
public static IEnumerable<FrameworkElement> GetFrameworkElementOwners(ResourceDictionary dictionary);
public static IEnumerable<FrameworkContentElement> GetFrameworkContentElementOwners(ResourceDictionary dictionary);
public static IEnumerable<Application> GetApplicationOwners(ResourceDictionary dictionary);
These methods return an empty enumerable unless VisualDiagnostics is enabled and the ENABLE_XAML_DIAGNOSTICS_SOURCE_INFO environment variable is set.
Finding StaticResource references
A diagnostic assistant can now receive a notification whenever a StaticResource reference is resolved. (The feature is for use by diagnostic assistants, not by production applications.) A diagnostic assistant such as Visual Studio’s “Edit-and-Continue” facility may want to update all uses of a resource when its value in a ResourceDictionary changes. WPF does this automatically for DynamicResource references, but it intentionally does not do so for StaticResource references. Starting with the .NET Framework 4.7.2, the diagnostic assistant can use these notifications to locate those uses of the static resource.
The notification is implemented by the new ResourceDictionaryDiagnostics.StaticResourceResolved event:
C#
public static event EventHandler<StaticResourceResolvedEventArgs> StaticResourceResolved;
This event is raised whenever the runtime resolves a StaticResource reference. The StaticResourceResolvedEventArgs arguments describe the resolution, and indicate the object and property that host the StaticResource reference and the ResourceDictionary and key used for the resolution:
C#
public class StaticResourceResolvedEventArgs : EventArgs
{
public Object TargetObject { get; }

public Object TargetProperty { get; }

public ResourceDictionary ResourceDictionary { get; }

public object ResourceKey { get; }
}
The event is not raised (and its add accessor is ignored) unless VisualDiagnostics is enabled and the ENABLE_XAML_DIAGNOSTICS_SOURCE_INFO environment variable is set.
ClickOnce
HDPI-aware applications for Windows Forms, Windows Presentation Foundation (WPF), and Visual Studio Tools for Office (VSTO) can all be deployed by using ClickOnce. If the following entry is found in the application manifest, deployment will succeed under .NET Framework 4.7.2:
XML
<windowsSettings>
<dpiAware xmlns=”http://schemas.microsoft.com/SMI/2005/WindowsSettings”>true</dpiAware>
</windowsSettings>
For Windows Forms application, the previous workaround of setting DPI awareness in the application configuration file rather than the application manifest is no longer necessary for ClickOnce deployment to succeed.

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

声明:大眼仔旭 | 本文采用[BY-NC-SA]协议进行授权
文章名称:《.NET 框架 Microsoft .NET Framework 4.7.2 中文离线安装包正式发布
文章固定链接:http://www.dayanzai.me/net-framework.html
本站资源仅供个人学习交流,请于下载后 24 小时内删除,不允许用于商业用途,否则法律问题自行承担。
转载声明
全部评论: (8条)
  1. AC2016-04-17 10:18 回复
    你好,怎么生成有水印啊?
  2. lung27892016-08-04 08:56 回复
    微軟必備!真是感謝大眼大大提供離線安裝版!支持與感謝~
  3. jerry2018-06-16 19:06 回复
    终于找到官方下载地址了,谢谢!!
1 2

发表评论

返回顶部