ms-dynamics.ru

Скачать net framework windows 7

What's new in the .NET Framework

This article summarizes key new скачать net framework windows 7 and improvements in the following versions of the .NET Framework:

.NET Framework 4.7.2
.NET Скачать net framework windows 7 4.7.1
.NET Framework 4.7
.NET Framework 4.6.2
.NET Framework 4.6.1
.NET 2015 and .NET Framework 4.6
.NET Framework 4.5.2
.NET Framework 4.5.1
.NET Framework 4.5

This article does not provide comprehensive information about each new feature and is subject to change.

For general information about the .NET Framework, see Getting Started. For supported platforms, see System Requirements. For download links and installation instructions, see Installation Guide.

Introducing the .NET Framework 4.7.2

The .NET Framework 4.7.2 builds on previous versions of the .NET Framework 4.x by adding many new fixes and several new features while remaining a very stable product.

Downloading and installing the .NET Framework 4.7.2

You can download the .NET Framework 4.7.2 from the following locations:

The .NET Framework 4.7.2 can be installed on Windows 10, Windows 8.1, Windows 7 SP1, and the corresponding server platforms starting with Windows Server 2008 R2 SP1.

You can install the .NET Framework 4.7.2 by using either the скачать net framework windows 7 installer or the offline installer. The recommended way for most users is to use the web installer.

You can target the .NET Framework 4.7.2 in Visual Studio 2012 or later by installing the .NET Framework 4.7.2 Developer Pack.

What's new in the .NET Framework 4.7.2

The .NET Framework 4.7.2 includes new features in the following areas:

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 скачать net framework windows 7 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 скачать net framework windows 7 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:

with code like this:

The Скачать net framework windows 7 and RSA.Create(Int32) methods let you generate new DSA or RSA keys with a specific key size. For example:

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:

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 скачать net framework windows 7 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 скачать net framework windows 7 with the .NET Framework 4.7.2, the SignerInfo class exposes more information about the скачать net framework windows 7.

You can retrieve the value of the Скачать net framework windows 7 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:

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 скачать net framework windows 7 running under .NET Framework 4.7.2 can opt into this behavior by adding the following AppContext switch to the application configuration file:

Additional collection APIs

The .NET Framework 4.7.2 adds a number of скачать net framework windows 7 APIs to the SortedSet<T> and HashSet<T> types.

These include:

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.

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 скачать net framework windows 7 changed.

When developing ASP.NET applications that target the .NET Framework 4.7.2, you can:

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 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:

You can also configure SameSite cookies at the application level by modifying the web.config file:

You can add SameSite for FormsAuthentication and System.Web.SessionState cookies by modifying the web config file:

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:

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 скачать net framework windows 7 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 Скачать net framework windows 7.

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:

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:

The basic flow of скачать net framework windows 7 Always Encrypted is:

  1. 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.

  2. Once the enclave has been attested, the driver establishes a secure channel with the secure enclave hosted on SQL Server.

  3. 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 Скачать net framework windows 7 whose content is copied from a given source URI:

A diagnostic assistant that edits the original markup in MyRD.xaml can use the new feature to locate the dictionary.

Скачать net framework windows 7 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:

The method returns an empty enumerable unless VisualDiagnostics is enabled and the 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 property refers to the dictionary (either directly, or indirectly via the ResourceDictionary.MergedDictionaries property).

Three new static methods implemented on скачать net framework windows 7 System.Windows.Diagnostics.ResourceDictionaryDiagnostics class, one for each of the base types that has a property, support this step:

These methods return an empty enumerable unless VisualDiagnostics is enabled and the 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 скачать net framework windows 7. 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:

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:

The event is not raised (and its accessor is ignored) unless VisualDiagnostics is enabled and the environment variable is set.

ClickOnce

HDPI-aware applications for Windows Forms, Windows Presentation Foundation (WPF), and Visual Studio Tools for Office (VSTO) can all скачать net framework windows 7 deployed скачать net framework windows 7 using ClickOnce.

If the following entry is found in the application manifest, deployment will succeed under .NET Framework 4.7.2:

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.

What's new in the .NET Framework 4.7.1

The .NET Framework 4.7.1 includes new features in the following areas:

In addition, a major focus in the .NET Framework 4.7.1 is improved accessibility, which allows an application to provide an appropriate experience for users of Assistive Technology.

For information on accessibility improvements in the .NET Framework 4.7.1, see What's new in accessibility in the .NET Framework.

Core

Support for .NET Standard 2.0

.NET Standard defines a set of APIs that must be available on each .NET implementation that скачать net framework windows 7 that version of скачать net framework windows 7 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 скачать net framework windows 7 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 windows 7 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.

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, скачать net framework windows 7 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 скачать net framework windows 7.

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 скачать net framework windows 7 .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:

What's new in the .NET Framework 4.7

The .NET Framework 4.7 includes new features in the following areas:

For a list of new APIs added to the .NET Framework 4.7, see .NET Framework 4.7 API Changes on GitHub.

For a list of скачать net framework windows 7 improvements and bug fixes скачать net framework windows 7 the .NET Framework 4.7, see .NET Framework 4.7 List of Changes on GitHub. For additional information, see Announcing the .NET Framework 4.7 in the .NET blog.

Core

The .NET Framework 4.7 improves serialization by the DataContractJsonSerializer:

Enhanced functionality with Elliptic Curve Cryptography (ECC)*

In the .NET Framework 4.7, methods were added to the ECDsa and ECDiffieHellman classes to allow for an object to represent an already-established key.

An method was also added for exporting the key using explicit curve parameters.

The .NET Framework 4.7 also adds support for additional curves (including the Brainpool curve suite), and has added predefined definitions for ease-of-creation through the new Create and Create factory methods.

You can see an example of .NET Framework 4.7 cryptography improvements on GitHub.

Better support for control characters by the DataContractJsonSerializer

In the .NET Framework 4.7, the DataContractJsonSerializer serializes control characters in conformity with the ECMAScript 6 standard.

This behavior is enabled by default for applications that target the .NET Framework 4.7, and is an opt-in feature for applications that are скачать net framework windows 7 under the .NET Framework 4.7 but target a previous version of the .NET Framework.

For more information, see Retargeting Changes in the .NET Framework 4.7.

Networking

The .NET Framework 4.7 adds the following network-related feature:

Default operating system support for TLS protocols*

The TLS stack, which is used by System.Net.Security.SslStream and up-stack components such as HTTP, FTP, and SMTP, allows developers to use the default TLS protocols supported by the operating system.

Developers need no longer hard-code a TLS version.

ASP.NET

In the .NET Framework 4.7, ASP.NET includes the following new features:

Object Cache Extensibility

Starting with the .NET Framework 4.7, ASP.NET adds a new set of APIs that allow developers to replace the default ASP.NET implementations for in-memory object caching and скачать net framework windows 7 monitoring.

Developers can now replace any of the following three components if the ASP.NET implementation is not adequate:

  • Object Cache Store.

    By using the new cache providers configuration section, developers can plug in new implementations of an object cache for an ASP.NET application by using the new ICacheStoreProvider interface.

  • Memory monitoring. The default memory monitor in ASP.NET notifies applications when they are running close to the configured private bytes limit for the process, or when the machine is low on total available physical RAM.

    When these limits are near, notifications are fired. For some applications, notifications are fired too close to the configured limits to allow for скачать net framework windows 7 reactions. Developers can now write their own memory monitors to replace the default by using the ApplicationMonitors.MemoryMonitor property.

  • Memory Limit Reactions.

    By default, ASP.NET attempts to trim the object cache and periodically call GC.Collect when the private byte скачать net framework windows 7 limit is near. For some applications, the frequency of calls to GC.Collect or the amount of cache that is trimmed are inefficient.

    Developers can now replace or supplement the default скачать net framework windows 7 by subscribing IObserver implementations to the application's memory monitor.

Windows Communication Foundation (WCF)

Windows Communication Foundation (WCF) adds the following features and changes:

Ability to configure the default message security settings to TLS 1.1 or TLS 1.2

Starting with the .NET Framework 4.7, WCF allows you to configure TSL 1.1 or TLS 1.2 in addition to SSL 3.0 and TSL 1.0 as the default message security protocol.

This is an opt-in setting; to enable it, you must add the following entry to your application configuration file:

Improved reliability of WCF applications and WCF serialization

WCF includes a number of code changes that eliminate race conditions, thereby improving performance and the reliability of serialization options. These include:

  • Better support for mixing asynchronous and synchronous code in calls to SocketConnection.BeginRead and SocketConnection.Read.
  • Improved reliability when aborting a connection with SharedConnectionListener and DuplexChannelBinder.
  • Improved reliability of serialization operations when calling the FormatterServices.GetSerializableMembers(Type) method.
  • Improved reliability when removing a waiter by calling the ChannelSynchronizer.RemoveWaiter method.

Windows Forms

In the .NET Framework 4.7, Windows Forms improves support for high DPI monitors.

High DPI support

Starting with applications that target the .NET Framework 4.7, the .NET Framework features high DPI and dynamic DPI support for Windows Forms applications.

High DPI support improves the layout and appearance of forms and controls on high DPI monitors. Dynamic DPI changes the layout and appearance of forms and controls when the user changes the DPI or display scale factor of a running application.

High DPI support is an opt-in feature that you configure by defining a <System.Windows.Forms.ConfigurationSection> section in your application configuration file. For more information on adding high DPI support and dynamic DPI support to your Windows Forms application, see High DPI Support in Windows Forms.

Windows Presentation Foundation (WPF)

In the .NET Framework 4.7, Скачать net framework windows 7 includes the following enhancements:

Support for a touch/stylus stack based on Windows WM_POINTER messages

You now have the option of using a touch/stylus stack based on WM_POINTER messages instead of the Windows Ink Services Platform (WISP).

This is an opt-in feature in the .NET Framework. For more information, see Retargeting Скачать net framework windows 7 in the .NET Framework 4.7.

New implementation for WPF printing APIs

WPF's printing APIs скачать net framework windows 7 the System.Printing.PrintQueue class call the Windows Print Document Package API instead of the deprecated XPS Print API. For the impact of this change on application compatibility, see Retargeting Changes in the .NET Framework 4.7.

What's new in the .NET Framework 4.6.2

The .NET Framework 4.6.2 includes new features in the following areas:

For a list of new APIs added to the .NET Framework 4.6.2, see .NET Framework 4.6.2 API Changes on GitHub. For a list of feature improvements and bug fixes in the .NET Framework 4.6.2, see .NET Framework 4.6.2 List of Changes on GitHub.

For additional information, see Announcing .NET Framework 4.6.2 in the .NET blog.

ASP.NET

In the .NET Framework 4.6.2, ASP.NET includes the following enhancements:

Improved support for localized error messages in data annotation validators

Data annotation validators enable you to perform validation by adding one or more attributes to a class property.

The attribute's ValidationAttribute.ErrorMessage element defines the text of the error message if validation fails. Starting with the .NET Framework 4.6.2, ASP.NET makes it easy to localize error messages. Error messages will be localized if:

  1. The ValidationAttribute.ErrorMessage is provided in the validation attribute.

  2. The resource file is stored in the App_LocalResources folder.

  3. The name of the скачать net framework windows 7 resources file has the form name, where name is a culture name in the format languageCodecountry/regionCode or languageCode.

  4. The key name of the resource is the string assigned to the ValidationAttribute.ErrorMessage attribute, and its value is the localized error message.

For example, the following data annotation attribute defines the default culture's error message for an invalid rating.

You can then create a resource file, DataAnnotation.Localization.fr.resx, whose key is the error message string and whose value is the localized error message.

The file must be found in the folder. For example, the following is the key and its value in a localized French (fr) language error message:

NameValue
The rating скачать net framework windows 7 be between 1 and 10.La note doit être скачать net framework windows 7 entre скачать net framework windows 7 et 10.

This file can then

In addition, data annotation localization is extensible.

Developers can plug in their own string localizer provider by implementing the IStringLocalizerProvider interface to store localization string somewhere other than in a resource file.

Async support with скачать net framework windows 7 store providers

ASP.NET now allows task-returning methods to be used with session-state store providers, thereby allowing ASP.NET apps to get the scalability benefits of async.

To supports asynchronous operations with session state store providers, ASP.NET includes a new interface, System.Web.SessionState.ISessionStateModule, which inherits from IHttpModule and allows developers to implement their own session-state module and async session store providers. The interface is defined as follows:

In addition, the SessionStateUtility class includes two new methods, IsSessionStateReadOnly and IsSessionStateRequired, that can be used to support asynchronous operations.

Async support for output-cache providers

Starting with the .NET Framework 4.6.2, task-returning methods can be used with output-cache providers to provide the scalability benefits of async.

Providers that implement these methods reduce thread-blocking on a web server and improve the scalability of an ASP.NET service.

The following APIs have been added to скачать net framework windows 7 asynchronous output-cache providers:

  • The System.Web.Caching.OutputCacheProviderAsync class, which inherits from System.Web.Caching.OutputCacheProvider and allows developers to implement an asynchronous output-cache provider.

  • The OutputCacheUtility class, which provides helper methods for configuring the output cache.

  • 18 new methods in the System.Web.HttpCachePolicy class.

    These include GetCacheability, GetCacheExtensions, GetETag, GetETagFromFileDependencies, GetMaxAge, GetMaxAge, GetNoStore, GetNoTransforms, GetOmitVaryStar, GetProxyMaxAge, GetRevalidation, GetUtcLastModified, GetVaryByCustom, HasSlidingExpiration, and IsValidUntilExpires.

  • 2 new methods in the System.Web.HttpCacheVaryByContentEncodings class: GetContentEncodings and SetContentEncodings.

  • 2 new methods in the System.Web.HttpCacheVaryByHeaders class: GetHeaders and SetHeaders.

  • 2 new methods in the System.Web.HttpCacheVaryByParams class: GetParams and SetParams.

  • In the System.Web.Caching.AggregateCacheDependency class, the GetFileDependencies method.

  • In the CacheDependency, the GetFileDependencies method.

Character categories

Characters in the .NET Framework 4.6.2 are classified based on the Unicode Standard, Version 8.0.0.

In .NET Framework 4.6 and .NET Framework 4.6.1, characters were classified based on Unicode 6.3 character categories.

Support for Unicode 8.0 is limited to the classification of characters by the CharUnicodeInfo class and to types and methods that rely on it. These include the StringInfo class, the overloaded Char.GetUnicodeCategory method, and the character classes recognized by the .NET Framework regular expression engine.

Character and string comparison and sorting is unaffected by this change and continues to rely on the underlying operating system or, on Windows 7 systems, on character data provided by the .NET Framework.

For changes in character categories from Unicode 6.0 to Unicode 7.0, see The Unicode Standard, Version 7.0.0 at The Unicode Consortium website.

For changes from Unicode 7.0 to Unicode 8.0, see The Unicode Standard, Version 8.0.0 at The Unicode Consortium скачать net framework windows 7 for X509 certificates containing FIPS 186-3 DSA

The .NET Framework 4.6.2 adds support for DSA (Digital Signature Algorithm) X509 certificates whose keys exceed the FIPS 186-2 1024-bit limit.

In addition to supporting the larger key sizes of FIPS 186-3, the .NET Framework 4.6.2 allows computing signatures with the SHA-2 family of hash algorithms (SHA256, SHA384, and SHA512).

FIPS 186-3 support is provided by the new System.Security.Cryptography.DSACng class.

In keeping with recent changes to the RSA class in the .NET Framework 4.6 and the ECDsa class in the .NET Framework 4.6.1, the DSA abstract base class in .NET Скачать net framework windows 7 4.6.2 has additional methods to allow callers to use this functionality without casting. You can call the DSACertificateExtensions.GetDSAPrivateKey extension method to sign data, as the following example shows.

And you can call the DSACertificateExtensions.GetDSAPublicKey extension method to verify signed data, as the following example shows.

Increased clarity for inputs to ECDiffieHellman key derivation routines

The .NET Framework 3.5 added support for Ellipic Curve Diffie-Hellman Key Agreement with three different Key Derivation Function (KDF) routines.

The inputs to the routines, and the routines themselves, were configured via properties on the ECDiffieHellmanCng object. But since not every routine read every input property, there was ample room for confusion on the past of the developer.

To address this in the .NET Framework 4.6.2, the following three methods have been added to the ECDiffieHellman base class to more clearly represent these KDF routines and their inputs:

ECDiffieHellman methodDescription
DeriveKeyFromHash(ECDiffieHellmanPublicKey, HashAlgorithmName, Byte[], Byte[])Derives key скачать net framework windows 7 using the formula

HASH(secretPrepend || x || secretAppend)

HASH(secretPrepend OrElse x OrElse secretAppend)

where x is the computed result of the EC Diffie-Hellman algorithm.
DeriveKeyFromHmac(ECDiffieHellmanPublicKey, HashAlgorithmName, Byte[], Byte[], Byte[])Derives key material using the formula

Скачать net framework windows 7, secretPrepend || x || secretAppend)

HMAC(hmacKey, secretPrepend OrElse x OrElse secretAppend)

where x is the computed result of the EC Diffie-Hellman algorithm.
DeriveKeyTls(ECDiffieHellmanPublicKey, Byte[], Byte[])Derives key material using the TLS pseudo-random function (PRF) derivation algorithm.

Support for persisted-key symmetric encryption

The Windows cryptography library (CNG) added support for storing persisted symmetric keys and using hardware-stored symmetric keys, and the .NET Framework 4.6.2 mades it possible for developers to make use of this feature.

Since the notion of key names and key providers is скачать net framework windows 7, using this feature requires utilizing the constructor of the concrete implementation types instead of the preferred factory approach (such as calling ).

Persisted-key symmetric encryption support exists for the AES (AesCng) and 3DES (TripleDESCng) algorithms. For example:

SignedXml support for SHA-2 hashing

The .NET Framework 4.6.2 adds support to the SignedXml class for RSA-SHA256, RSA-SHA384, and RSA-SHA512 PKCS#1 signature methods, and SHA256, SHA384, and SHA512 reference digest algorithms.

The URI constants are all exposed on SignedXml:

Any programs that have registered a custom SignatureDescription handler into CryptoConfig to add support for these algorithms will continue to function as they did in the past, but since there are now platform defaults, the CryptoConfig registration is no longer necessary.

SqlClient

.NET Framework Data Provider for SQL Server (System.Data.SqlClient) includes the following new features in the .NET Framework 4.6.2:

Connection pooling and timeouts with Azure SQL databases

When скачать net framework windows 7 pooling is enabled and a timeout or other login error occurs, an exception is cached, and the cached exception is thrown on any subsequent connection attempt for the next 5 seconds to 1 minute.

скачать net framework windows 7

For more details, see SQL Server Connection Pooling (ADO.NET).

This behavior is not desirable when connecting to Azure SQL Databases, since connection attempts can fail with transient errors that are typically recovered quickly. To better optimize the connection retry experience, the connection pool blocking period behavior is removed when connections скачать net framework windows 7 Azure SQL Databases fail.

The addition of the new keyword lets you to select the blocking period best suited for your app.

Values include:

The connection pool blocking period for an application that connects to an Azure SQL Database is disabled, and the connection pool blocking period for an application that connects to any other SQL Server instance is enabled. This is the default value. If the Server endpoint name ends with any of the following, they are considered Azure SQL Databases:

  • .database.windows.net

  • .database.chinacloudapi.cn

  • .database.usgovcloudapi.net

  • .database.cloudapi.de

Скачать net framework windows 7 connection pool blocking period is always enabled.

The connection pool blocking period is always disabled.

Enhancements for Always Encrypted

SQLClient introduces two enhancements for Скачать net framework windows 7 Encrypted:

  • To improve performance of parameterized queries against encrypted database columns, encryption metadata for query parameters is now cached.

    With the SqlConnection.ColumnEncryptionQueryMetadataCacheEnabled property set to (which is the default value), if the same query is called multiple times, the client retrieves parameter metadata from the server only once.

  • Column encryption key entries in the key cache are now evicted after a configurable time interval, set using the SqlConnection.ColumnEncryptionKeyCacheTtl property.

Windows Communication Foundation

In the .NET Framework 4.6.2, Windows Communication Foundation has been enhanced in the following areas:

WCF transport security support for certificates stored using CNG

WCF transport скачать net framework windows 7 supports certificates stored using the Windows cryptography library (CNG).

In the .NET Framework 4.6.2, this support is limited to using certificates with a public key that has an exponent no more than 32 bits in length. When an application targets the .NET Framework 4.6.2, this feature скачать net framework windows 7 on by default.

For applications that target the .NET Framework 4.6.1 and earlier but are running on the .NET Framework 4.6.2, this feature can be enabled by adding the following line to the <runtime> section of the app.config or web.config file.

This can also be done programmatically with code like the following:

Better support for multiple daylight saving time adjustment rules by the DataContractJsonSerializer class

Customers can use an application configuration setting to determine whether the DataContractJsonSerializer class supports multiple adjustment rules for a single time zone.

This is an opt-in feature. To enable it, add the following setting to your app.config file:

When this feature is enabled, a DataContractJsonSerializer object uses the TimeZoneInfo type instead of the TimeZone type to deserialize date and time data. TimeZoneInfo скачать net framework windows 7 multiple adjustment rules, which makes it possible to work with historic time zone data; TimeZone does not.

For more information on the TimeZoneInfo structure and time zone adjustments, see Time Zone Overview.

NetNamedPipeBinding best match

WCF has a new app setting that can be set on client applications to ensure they always connect скачать net framework windows 7 the service listening on the URI that best matches the one that they request.

With this app setting set to (the default), it is possible for clients using NetNamedPipeBinding to attempt to connect to a service listening on a URI that is a substring of the requested URI.

For example, a client tries to connect to a service listening atbut a different service on that machine running with administrator privilege is listening at

Источник: https://docs.microsoft.com/en-us/dotnet/framework/whats-new/