Download microsoft framework 4.5.1 for free. Development Tools downloads - Microsoft.NET Framework by Microsoft and many more programs are available for instant and free download. The.NET Framework for PC is a development platform for building apps for web, Windows, Windows Phone, Windows Server, and Microsoft Azure. It consists of the common language runtime (CLR) and the.NET Framework class library, which includes a broad range of functionality and support for many industry standards. Windows 7 Forums is the largest help and support community. Had the same problem with.NET framework 4.5.1 update; the problem turned out to be that the C: Program Data Microsoft Net Framework directory didn't have the right permissions to be able to be written to by the installer. Download size: 12.8 MB cbs.zip is 35mb max upload limit.
- Download Net Framework 4.5.1 For Windows 7
- Net Framework 4.5 1 Deutsch Download For Windows 7
- .net Framework 4.5.1 Download Windows 7
- Latest Version:.NET Framework Version 4.8 LATEST
- Requirements:Windows 8 / Windows 10 / Windows 8 64 / Windows 10 64
- Author / Product:Microsoft Corporation / .NET Framework (4)
- Old Versions:
- Filename:ndp48-x86-x64-allos-enu.exe
- MD5 Checksum:4e7a8586d06ce1f8cebac0d4bc379e16
- Details:.NET Framework (4) 2019 full offline installer setup for PC
The .NET Framework is Microsoft's comprehensive and consistent programming model for building applications that have visually stunning user experiences, seamless and secure communication, and the ability to model a range of business processes. The Microsoft .NET Framework 4 redistributable package installs the .NET Framework runtime and associated files that are required to run and develop applications to target the .NET Framework 4.
Detect & update more rare, mismatched and outdated PC drivers with 1-click. Download Driver Booster Pro!
The .NET Framework 4 works side by side with older Framework versions. Applications that are based on earlier versions of the Framework will continue to run on the version targeted by default. Version 4.5.1 built upon successes of the previous milestone releases v4 (which among other things enabled developers to optimize their apps for parallel computing or distributed systems) and v4.5 (which for the first time enabled developers to start developing Metro-style apps for Windows 8, Windows RT and Windows Phone software environments).
The .NET Framework for PC is a development platform for building apps for web, Windows, Windows Phone, Windows Server, and Microsoft Azure. It consists of the common language runtime (CLR) and the .NET Framework class library, which includes a broad range of functionality and support for many industry standards.
Microsoft .NET Framework provides many services, including memory management, type and memory safety, security, networking, and application deployment. It provides easy-to-use data structures and APIs that abstract the lower-level Windows operating system. You can use a variety of programming languages with the .NET Framework, including C#, F#, and Visual Basic.
The .NET Framework comes with Windows PC, enabling you to run .NET Framework applications. You may need a later version of the .NET Framework than comes with your Windows version.
-->Detect & update more rare, mismatched and outdated PC drivers with 1-click. Download Driver Booster Pro!
The .NET Framework 4 works side by side with older Framework versions. Applications that are based on earlier versions of the Framework will continue to run on the version targeted by default. Version 4.5.1 built upon successes of the previous milestone releases v4 (which among other things enabled developers to optimize their apps for parallel computing or distributed systems) and v4.5 (which for the first time enabled developers to start developing Metro-style apps for Windows 8, Windows RT and Windows Phone software environments).
The .NET Framework for PC is a development platform for building apps for web, Windows, Windows Phone, Windows Server, and Microsoft Azure. It consists of the common language runtime (CLR) and the .NET Framework class library, which includes a broad range of functionality and support for many industry standards.
Microsoft .NET Framework provides many services, including memory management, type and memory safety, security, networking, and application deployment. It provides easy-to-use data structures and APIs that abstract the lower-level Windows operating system. You can use a variety of programming languages with the .NET Framework, including C#, F#, and Visual Basic.
The .NET Framework comes with Windows PC, enabling you to run .NET Framework applications. You may need a later version of the .NET Framework than comes with your Windows version.
Introduction
Runtime changes affect all apps that are running under a .NET Framework it was not compiled against and that use a particular feature.
In the topics that describe runtime changes, we have classified individual items by their expected impact, as follows:
MajorThis is a significant change that affects a large number of apps or that requires substantial modification of code.
MinorThis is a change that affects a small number of apps or that requires minor modification of code.
Edge caseThis is a change that affects apps under very specific scenarios that are not common.
TransparentThis is a change that has no noticeable effect on the app's developer or user. The app should not require modification because of this change.
If you are migrating from the .NET Framework 4.5.1 to 4.7.2, review the following topics for application compatibility issues that may affect your app:
ASP.NET
ASP.NET MVC now escapes spaces in strings passed in via route parameters
Details | In order to conform to RFC 2396, spaces in route paths are now escaped when populating action parameters from a route. So, whereas /controller/action/some data would previously match the route /controller/action/{data} and provide some data as the data parameter, it will now provide some%20data instead. |
Suggestion | Code should be updated to unescape string parameters from a route. If the original URI is needed, it can be accessed with the RequestUri.OriginalString API. |
Scope | Minor |
Version | 4.5.2 |
Type | Runtime |
Affected APIs |
GridViews with AllowCustomPaging set to true may fire the PageIndexChanging event when leaving the final page of the view
Details | A bug in the .NET Framework 4.5 causes PageIndexChanging to sometimes not fire for GridViews that have enabled AllowCustomPaging. |
Suggestion | This issue has been fixed in the .NET Framework 4.6 and may be addressed by upgrading to that version of the .NET Framework. As a work-around, the app can do an explicit BindGrid on any Page_Load that would hit these conditions (the GridView is on the last page and LastPageSize is different from PageSize). Alternatively, the app can be modified to allow paging (instead of custom paging), as that scenario does not demonstrate the problem. |
Scope | Minor |
Version | 4.5 |
Type | Runtime |
Affected APIs |
No longer able to set EnableViewStateMac to false
Details | ASP.NET no longer allows developers to specify <pages enableViewStateMac='false'/> or <@Page EnableViewStateMac='false' %> . The view state message authentication code (MAC) is now enforced for all requests with embedded view state. Only apps that explicitly set the EnableViewStateMac property to false are affected. |
Suggestion | EnableViewStateMac must be assumed to be true, and any resulting MAC errors must be resolved (as explained in this guidance, which contains multiple resolutions depending on the specifics of what is causing MAC errors). |
Scope | Major |
Version | 4.5.2 |
Type | Runtime |
Profiling ASP.Net MVC4 apps can lead to Fatal Execution Engine Error
Details | Profilers using NGEN /Profile assemblies may crash profiled ASP.NET MVC4 applications on startup with a 'Fatal Execution Engine Exception' |
Suggestion | This issue is fixed in the .NET Framework 4.5.2. Alternatively, the profiler may avoid this issue by specifying COR_PRF_DISABLE_ALL_NGEN_IMAGES in its event mask. |
Scope | Edge |
Version | 4.5 |
Type | Runtime |
Core
A ConcurrentDictionary serialized in .NET Framework 4.5 with NetDataContractSerializer cannot be deserialized by .NET Framework 4.5.1 or 4.5.2
Details | Due to internal changes to the type, ConcurrentDictionary<TKey,TValue> objects that are serialized with the .NET Framework 4.5 using the NetDataContractSerializer cannot be deserialized in the .NET Framework 4.5.1 or in the .NET Framework 4.5.2.Note that moving in the other direction (serializing with the .NET Framework 4.5.x and deserializing with the .NET Framework 4.5) works. Similarly, all 4.x cross-version serialization works with the .NET Framework 4.6.Serializing and deserializing with a single version of the .NET Framework is not affected. |
Suggestion | If it is necessary to serialize and deserialize a ConcurrentDictionary<TKey,TValue> between the .NET Framework 4.5 and .NET Framework 4.5.1/4.5.2, an alternate serializer like the DataContractSerializer or BinaryFormatter serializer should be used instead of the NetDataContractSerializer.Alternatively, because this issue is addressed in the .NET Framework 4.6, it may be solved by upgrading to that version of the .NET Framework. |
Scope | Minor |
Version | 4.5.1 |
Type | Runtime |
Allow Unicode in URIs that resemble UNC shares
Details | In System.Uri, constructing a file URI containing both a UNC share name and Unicode characters will no longer result in a URI with invalid internal state. The behavior will change only when all of the following are true:
|
Suggestion | Applications working with URIs consistently containing Unicode could have conceivably used this behavior to disallow references to UNC shares. Those applications should use IsUnc instead. |
Scope | Edge |
Version | 4.7.2 |
Type | Runtime |
Affected APIs |
AppDomainSetup.DynamicBase is no longer randomized by UseRandomizedStringHashAlgorithm
Details | Prior to the .NET Framework 4.6, the value of DynamicBase would be randomized between application domains, or between processes, if UseRandomizedStringHashAlgorithm was enabled in the app's config file. Beginning in the .NET Framework 4.6, DynamicBase will return a stable result between different instances of an app running, and between different app domains. Dynamic bases will still differ for different apps; this change only removes the random naming element for different instances of the same app. |
Suggestion | Be aware that enabling UseRandomizedStringHashAlgorithm will not result in DynamicBase being randomized. If a random base is needed, it must be produced in your app's code rather than via this API. |
Scope | Edge |
Version | 4.6 |
Type | Runtime |
Affected APIs |
Calling Attribute.GetCustomAttributes on an indexer property no longer throws AmbiguousMatchException if the ambiguity can be resolved by index's type
Details | Prior to the .NET Framework 4.6, calling GetCustomAttribute(s) on an indexer property which differed from another property only by the type of the index would result in an AmbiguousMatchException. Beginning in the .NET Framework 4.6, the property's attributes will be correctly returned. |
Suggestion | Be aware that GetCustomAttribute(s) will work more frequently now. If an app was previously relying on the AmbiguousMatchException, reflection should now be used to explicitly look for multiple indexers, instead. |
Scope | Edge |
Version | 4.6 |
Type | Runtime |
Affected APIs |
COR_PRF_GC_ROOT_HANDLEs are not being enumerated by profilers
Details | In the .NET Framework v4.5.1, the profiling API RootReferences2() is incorrectly never returning COR_PRF_GC_ROOT_HANDLE (they are returned as COR_PRF_GC_ROOT_OTHER instead). This issue is fixed beginning in the .NET Framework 4.6. |
Suggestion | This issue has been fixed in the .NET Framework 4.6 and may be addressed by upgrading to that version of the .NET Framework. |
Scope | Minor |
Version | 4.5.1 |
Type | Runtime |
ETW EventListeners do not capture events from providers with explicit keywords (like the TPL provider)
Details | ETW EventListeners with a blank keyword mask do not properly capture events from providers with explicit keywords. In the .NET Framework 4.5, the TPL provider began providing explicit keywords and triggered this issue. In the .NET Framework 4.6, EventListeners have been updated to no longer have this issue. |
Suggestion | To work around this problem, replace calls to EnableEvents(EventSource, EventLevel) with calls to the EnableEvents overload that explicitly specifies the 'any keywords' mask to use: EnableEvents(eventSource, level, unchecked((EventKeywords)0xFFFFffffFFFFffff)) .Alternatively, this issue has been fixed in the .NET Framework 4.6 and may be addressed by upgrading to that version of the .NET Framework. |
Scope | Edge |
Version | 4.5 |
Type | Runtime |
Affected APIs |
Persian calendar now uses the Hijri solar algorithm
Details | Starting with the .NET Framework 4.6, the PersianCalendar class uses the Hijri solar algorithm. Converting dates between the PersianCalendar and other calendars may produce a slightly different result beginning with the .NET Framework 4.6 for dates earlier than 1800 or later than 2023 (Gregorian).Also, PersianCalendar.MinSupportedDateTime is now March 22, 0622 instead of March 21, 0622 . |
Suggestion | Be aware that some early or late dates may be slightly different when using the PersianCalendar in .NET Framework 4.6. Also, when serializing dates between processes which may run on different .NET Framework versions, do not store them as PersianCalendar date strings (since those values may be different). |
Scope | Minor |
Version | 4.6 |
Type | Runtime |
Affected APIs |
Reflection objects can no longer be passed from managed code to out-of-process DCOM clients
Details | Reflection objects can no longer be passed from managed code to out-of-process DCOM clients. The following types are affected:
IMarshal for the object return E_NOINTERFACE . |
Suggestion | Update marshaling code to work with non-reflection objects |
Scope | Minor |
Version | 4.6 |
Type | Runtime |
Support special relative URI notation when Unicode is present
Details | Uri will no longer throw a NullReferenceException when calling TryCreate on certain relative URIs containing Unicode. The simplest reproduction of the NullReferenceException is below, with the two statements being equivalent:To reproduce the NullReferenceException, the following items must be true:
|
Suggestion | Users depending on this behavior to disallow relative URIs should instead specify UriKind.Absolute when creating a URI. |
Scope | Edge |
Version | 4.7.2 |
Type | Runtime |
Affected APIs |
TargetFrameworkName for default app domain no longer defaults to null if not set
Details | The TargetFrameworkName was previously null in the default app domain, unless it was explicitly set. Beginning in 4.6, the TargetFrameworkName property for the default app domain will have a default value derived from the TargetFrameworkAttribute (if one is present). Non-default app domains will continue to inherit their TargetFrameworkName from the default app domain (which will not default to null in 4.6) unless it is explicitly overridden. |
Suggestion | Code should be updated to not depend on TargetFrameworkName defaulting to null. If it is required that this property continue to evaluate to null, it can be explicitly set to that value. |
Scope | Edge |
Version | 4.6 |
Type | Runtime |
Affected APIs |
X509Certificate2.ToString(Boolean) does not throw now when .NET cannot handle the certificate
Details | In .NET Framework 4.5.2 and earlier versions, this method would throw if true was passed for the verbose parameter and there were certificates installed that weren't supported by the .NET Framework. Now, the method will succeed and return a valid string that omits the inaccessible portions of the certificate. |
Suggestion | Any code depending on X509Certificate2.ToString(Boolean) should be updated to expect that the returned string may exclude some certificate data (such as public key, private key, and extensions) in some cases in which the API would have previously thrown. |
Scope | Edge |
Version | 4.6 |
Type | Runtime |
Affected APIs |
Data
Connection pool blocking period for Azure SQL databases is removed
Details | Starting with the .NET Framework 4.6.2, for connection open requests to known Azure SQL databases (*.database.windows.net, *.database.chinacloudapi.cn, *.database.usgovcloudapi.net, *.database.cloudapi.de), the connection pool blocking period is removed, and connection open errors are not cached. Attempts to retry connection open requests will occur almost immediately after transient connection errors. This change allows the connection open attempt to be retried immediately for Azure SQL databases, thereby improving the performance of cloud- enabled apps. For all other connection attempts, the connection pool blocking period continues to be enforced. In the .NET Framework 4.6.1 and earlier versions, when an app encounters a transient connection failure when connecting to a database, the connection attempt cannot be retried quickly, because the connection pool caches the error and re-throws it for 5 seconds to 1 minute. For more information, see SQL Server Connection Pooling (ADO.NET). This behavior is problematic for connections to Azure SQL databases, which often fail with transient errors that are typically recovered from within a few seconds. The connection pool blocking feature means that the app cannot connect to the database for an extensive period, even though the database is available and the app needs to render within a few seconds. |
Suggestion | If this behavior is undesirable, the connection pool blocking period can be configured by setting the PoolBlockingPeriod property introduced in the .NET Framework 4.6.2. The value of the property is a member of the PoolBlockingPeriod enumeration that can take either of three values:The previous behavior can be restored by setting the PoolBlockingPeriod property to AlwaysBlock. |
Scope | Minor |
Version | 4.6.2 |
Type | Runtime |
Affected APIs |
SqlConnection.Open fails on Windows 7 with non-IFS Winsock BSP or LSP present
Details | Open() and OpenAsync(CancellationToken) fail in the .NET Framework 4.5 if running on a Windows 7 machine with a non-IFS Winsock BSP or LSP are present on the computer.To determine whether a non-IFS BSP or LSP is installed, use the netsh WinSock Show Catalog command, and examine every Winsock Catalog Provider Entry item that is returned. If the Service Flags value has the 0x20000 bit set, the provider uses IFS handles and will work correctly. If the 0x20000 bit is clear (not set), it is a non-IFS BSP or LSP. |
Suggestion | This bug has been fixed in the .NET Framework 4.5.2, so it can be avoided by upgrading the .NET Framework. Alternatively, it can be avoided by removing any installed non-IFS Winsock LSPs. |
Scope | Minor |
Version | 4.5 |
Type | Runtime |
Affected APIs |
Debugger
Null coalescer values are not visible in debugger until one step later
Details | A bug in the .NET Framework 4.5 causes values set via a null coalescing operation to not be visible in the debugger immediately after the assignment operation is executed when running on the 64-bit version of the Framework. |
Suggestion | Stepping one additional time in the debugger will cause the local/field's value to be correctly updated. Also, this issue has been fixed in the .NET Framework 4.6; upgrading to that version of the Framework should solve the issue. |
Scope | Edge |
Version | 4.5 |
Type | Runtime |
Entity Framework
EF no longer throws for QueryViews with specific characteristics
Details | Entity Framework no longer throws a StackOverflowException exception when an app executes a query that involves a QueryView with a 0.1 navigation property that attempts to include the related entities as part of the query. For example, by calling .Include(e => e.RelatedNavProp) . |
Suggestion | This change only affects code that uses QueryViews with 1-0.1 relationships when running queries that call .Include. It improves reliability and should be transparent to almost all apps. However, if it causes unexpected behavior, you can disable it by adding the following entry to the <appSettings> section of the app's configuration file: |
Scope | Edge |
Version | 4.5.2 |
Type | Runtime |
Opt-in break to revert from different 4.5 SQL generation to simpler 4.0 SQL generation
Details | Queries that produce JOIN statements and contain a call to a limiting operation without first using OrderBy now produce simpler SQL. After upgrading to .NET Framework 4.5, these queries produced more complicated SQL than previous versions. |
Suggestion | This feature is disabled by default. If Entity Framework generates extra JOIN statements that cause performance degradation, you can enable this feature by adding the following entry to the <appSettings> section of the application configuration (app.config) file: |
Scope | Transparent |
Version | 4.5.2 |
Type | Runtime |
Globalization
Unicode standard version 8.0 categories now supported
Details | In .NET Framework 4.6.2, Unicode data has been upgraded from Unicode Standard version 6.3 to version 8.0. When requesting Unicode character categories in .NET Framework 4.6.2, some results might not match the results in previous .NET Framework versions. This change mostly affects Cherokee syllables and New Tai Lue vowels signs and tone marks. |
Suggestion | Review code and remove/change logic that depends on hard-coded Unicode character categories. |
Scope | Minor |
Version | 4.6.2 |
Type | Runtime |
Affected APIs |
Networking
ContentDisposition DateTimes returns slightly different string
Details | String representations of ContentDisposition's have been updated, beginning in 4.6, to always represent the hour component of a DateTime with two digits. This is to comply with RFC822 and RFC2822. This causes ToString() to return a slightly different string in 4.6 in scenarios where one of the disposition's time elements was before 10:00 AM. Note that ContentDispositions are sometimes serialized via converting them to strings, so any ToString() operations, serialization, or GetHashCode calls should be reviewed. |
Suggestion | Do not expect that string representations of ContentDispositions from different .NET Framework versions will correctly compare to one another. Convert the strings back to ContentDispositions, if possible, before conducting a comparison. |
Scope | Minor |
Version | 4.6 |
Type | Runtime |
Affected APIs |
Runtime
Improved WCF chain trust certificate validation for Net.Tcp certificate authentication
Details | .NET Framework 4.7.2 improves chain trust certificate validation when using certificate authentication with transport security with WCF. With this improvement, client certificates that are used to authenticate to a server must be configured for client authentication. Similarly server certificates that are for the authenticating a server must be configured for server authentication. With this change, if the root certificate is disabled, the certificate chain validation fails. The same change was also made to .NET Framework 3.5 and later versions via Windows security roll-up. You can find more information here.This change is on by default and can be turned off by a configuration setting. |
Suggestion |
|
Scope | Minor |
Version | 4.7.2 |
Type | Runtime |
Security
RSACng.VerifyHash now returns False for any verification failure
Details | Starting with the .NET Framework 4.6.2, this method returns False if the signature itself is badly formatted. It now returns false for any verification failure.In the .NET Framework 4.6 and 4.6.1, the method throws a CryptographicException if the signature itself is badly formatted. |
Suggestion | Any code whose execution depends on handling the CryptographicException should instead execute if validation fails and the method returns False. |
Scope | Minor |
Version | 4.6.2 |
Type | Runtime |
Affected APIs |
SignedXml and EncryptedXml Breaking Changes
Details | In .NET Framework 4.6.2, Security fixes in SignedXml and EncryptedXml lead to different run-time behaviors. For example,
|
Suggestion | Developers might want to review the usage of XmlDsigXsltTransform and XmlDsigXsltTransform, as well as types derived from Transform since a document receiver may not be able to process it. |
Scope | Minor |
Version | 4.6.2 |
Type | Runtime |
Affected APIs |
Serialization
Exception message has changed for failed DataContract serialization in case of an unknown type
Details | Beginning in the .NET Framework 4.6, the exception message given if a DataContractSerializer or DataContractJsonSerializer fails to serialize or deserialize due to missing 'known types' has been clarified. |
Suggestion | Apps should not depend on specific exception messages. If an app depends on this message, either update it to expect the new message or (preferably) change it to depend only on the exception type. |
Scope | Edge |
Version | 4.6 |
Type | Runtime |
Affected APIs |
Setup and Deployment
Product versioning changes in the .NET Framework 4.6 and later versions
Details | Product versioning has changed from the previous releases of the .NET Framework, and particularly from the .NET Framework 4, 4.5, 4.5.1, and 4.5.2. The following are the detailed changes:
|
Suggestion | In general, applications should depend on the recommended techniques for detecting such things as the runtime version of the .NET Framework and the installation directory:
[!IMPORTANT] The subkey name is
|
Scope | Minor |
Version | 4.6 |
Type | Runtime |
The .NET Framework 4.6 does not use a 4.5.x.x version when registering itself in the registry
Details | As one might expect, the version key set in the registry (at HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftNET Framework SetupNDPv4Full ) for the .NET Framework 4.6 begins with '4.6', not '4.5'. Apps that depend on these registry keys to know which .NET Framework versions are installed on a machine should be updated to understand that 4.6 is a new possible version, and one that is compatible with previous 4.5.x releases. |
Suggestion | Update apps probing for a .NET Framework 4.5 install by looking for 4.5 registry keys to also accept 4.6. |
Scope | Edge |
Version | 4.6 |
Type | Runtime |
Tools
Contract.Invariant or Contract.Requires<TException> do not consider String.IsNullOrEmpty to be pure
Details | For apps that target the .NET Framework 4.6.1, if the invariant contract for Contract.Invariant or the precondition contract for Requires calls the String.IsNullOrEmpty method, the rewriter emits compiler warning CC1036: 'Detected call to method 'System.String.IsNullOrWhteSpace(System.String)' without [Pure] in method.' This is a compiler warning rather than a compiler error. |
Suggestion | This behavior was addressed in GitHub Issue #339. To eliminate this warning, you can download and compile an updated version of the source code for the Code Contracts tool from GitHub. Download information is found at the bottom of the page. |
Scope | Minor |
Version | 4.6.1 |
Type | Runtime |
Affected APIs |
Web Applications
'dataAnnotations:dataTypeAttribute:disableRegEx' app setting is on by default in .NET Framework 4.7.2
Details | In .NET Framework 4.6.1, an app setting ('dataAnnotations:dataTypeAttribute:disableRegEx' ) was introduced that allows users to disable the use of regular expressions in data type attributes (such as System.ComponentModel.DataAnnotations.EmailAddressAttribute, System.ComponentModel.DataAnnotations.UrlAttribute, and System.ComponentModel.DataAnnotations.PhoneAttribute). This helps to reduce security vulnerability such as avoiding the possibility of a Denial of Service attack using specific regular expressions.In .NET Framework 4.6.1, this app setting to disable RegEx usage was set to false by default. Staring with .NET Framework 4.7.2, this config switch is set to true by default to further reduce secure vulnerability for web applications that target .NET Framework 4.7.2 and above. |
Suggestion | If you find that regular expressions in your web application do not work after upgrading to .NET Framework 4.7.2, you can update the value of the 'dataAnnotations:dataTypeAttribute:disableRegEx' setting to false to revert to the previous behavior. |
Scope | Minor |
Version | 4.7.2 |
Type | Runtime |
Windows Communication Foundation (WCF)
Remove Ssl3 from the WCF TransportDefaults
Details | When using NetTcp with transport security and a credential type of certificate, the SSL 3 protocol is no longer a default protocol used for negotiating a secure connection. In most cases there should be no impact to existing apps as TLS 1.0 has always been included in the protocol list for NetTcp. All existing clients should be able to negotiate a connection using at least TLS1.0. |
Suggestion | If Ssl3 is required, use one of the following configuration mechanisms to add Ssl3 to the list of negotiated protocols.
|
Scope | Edge |
Version | 4.6.2 |
Type | Runtime |
Affected APIs |
WCF AddressHeaderCollection now throws an ArgumentException if an addressHeader element is null
Details | Starting with the .NET Framework 4.7.1, the AddressHeaderCollection(IEnumerable<AddressHeader>) constructor throws an ArgumentException if one of the elements is null . In the .NET Framework 4.7 and earlier versions, no exception is thrown. |
Suggestion | If you encounter compatibility issues with this change on the .NET Framework 4.7.1 or a later version, you can opt-out of it by adding the following line to the <runtime> section of the app.config file:: |
Scope | Minor |
Version | 4.7.1 |
Type | Runtime |
Affected APIs |
WCF MsmqSecureHashAlgorithm default value is now SHA256
Details | Starting with the .NET Framework 4.7.1, the default message signing algorithm in WCF for Msmq messages is SHA256. In the .NET Framework 4.7 and earlier versions, the default message signing algorithm is SHA1. |
Suggestion | If you run into compatibility issues with this change on the .NET Framework 4.7.1 or later, you can opt-out the change by adding the following line to the <runtime> section of your app.config file: |
Scope | Minor |
Version | 4.7.1 |
Type | Runtime |
WCF PipeConnection.GetHashAlgorithm now uses SHA256
Details | Starting with the .NET Framework 4.7.1, Windows Communication Foundation uses a SHA256 hash to generate random names for named pipes. In the .NET Framework 4.7 and earlier versions, it used a SHA1 hash. |
Suggestion | If you run into compatibility issue with this change on the .NET Framework 4.7.1 or later, you can opt-out it by adding the following line to the <runtime> section of your app.config file: |
Scope | Minor |
Version | 4.7.1 |
Type | Runtime |
WCF services that use NETTCP with SSL security and MD5 certificate authentication
Details | The .NET Framework 4.6 adds TLS 1.1 and TLS 1.2 to the WCF SSL default protocol list. When both client and server machines have the .NET Framework 4.6 or later installed, TLS 1.2 is used for negotiation.TLS 1.2 does not support MD5 certificate authentication. As a result, if a customer uses an MD5 certificate, the WCF client will fail to connect to the WCF service. |
Suggestion | You can work around this issue so that a WCF client can connect to a WCF server by doing any of the following:
[!WARNING] This workaround is not recommended, since a certificate with the MD5 hash algorithm is considered insecure.The following configuration file does this:
[!WARNING] This workaround is not recommended, since a certificate with the MD5 hash algorithm is considered insecure. |
Scope | Minor |
Version | 4.6 |
Type | Runtime |
Windows Presentation Foundation (WPF)
Accessing a WPF DataGrid's selected items from a handler of the DataGrid's UnloadingRow event can cause a NullReferenceException
Details | Due to a bug in the .NET Framework 4.5, event handlers for DataGrid events involving the removal of a row can cause a NullReferenceException to be thrown if they access the DataGrid's SelectedItem or SelectedItems properties. |
Suggestion | This issue has been fixed in the .NET Framework 4.6 and may be addressed by upgrading to that version of the .NET Framework. |
Scope | Minor |
Version | 4.5 |
Type | Runtime |
Affected APIs |
Calling DataGrid.CommitEdit from a CellEditEnding handler drops focus
Details | Calling CommitEdit() from one of the DataGrid's CellEditEnding event handlers causes the DataGrid to lose focus. |
Suggestion | This bug has been fixed in the .NET Framework 4.5.2, so it can be avoided by upgrading the .NET Framework. Alternatively, it can be avoided by explicitly re-selecting the DataGrid after calling CommitEdit(). |
Scope | Edge |
Version | 4.5 |
Type | Runtime |
Affected APIs |
Calling Items.Refresh on a WPF ListBox, ListView, or DataGrid with items selected can cause duplicate items to appear in the element
Details | In the .NET Framework 4.5, calling ListBox.Items.Refresh from code while items are selected in a ListBox can cause the selected items to be duplicated in the list. A similar issue occurs with ListView and DataGrid. This is fixed in the .NET Framework 4.6. |
Suggestion | This issue may be worked around by programatically unselecting items before Refresh() is called and then re-selecting them after the call is completed. Alternatively, this issue has been fixed in the .NET Framework 4.6 and may be addressed by upgrading to that version of the .NET Framework. |
Scope | Minor |
Version | 4.5 |
Type | Runtime |
Affected APIs |
Chained Popups with StaysOpen=False
Details | A Popup with StaysOpen=False is supposed to close when you click outside the Popup. When two or more such Popups are chained (i.e. one contains another), there were many problems, including:
|
Scope | Edge |
Version | 4.7.1 |
Type | Runtime |
Affected APIs |
Changing the IsEnabled property of the parent of a TextBlock control affects any child controls
Details | Starting with the .NET Framework 4.6.2, changing the IsEnabled property of the parent of a TextBlock control affects any child controls (such as hyperlinks and buttons) of the TextBlock control.In the .NET Framework 4.6.1 and earlier versions, controls inside a TextBlock did not always reflect the state of the IsEnabled property of the TextBlock parent. |
Suggestion | None. This change conforms to the expected behavior for controls inside a TextBlock control. |
Scope | Minor |
Version | 4.6.2 |
Type | Runtime |
Affected APIs |
Horizontal scrolling and virtualization
Details | This change applies to an ItemsControl that does its own virtualization in the direction orthogonal to the main scrolling direction (the chief example is DataGrid with EnableColumnVirtualization='True'). The outcome of certain horizontal scrolling operations has been changed to produce results that are more intuitive and more analogous to the results of comparable vertical operations. The operations include 'Scroll Here' and 'Right Edge', to use the names from the menu obtained by right-clicking a horizontal scrollbar. Both of these compute a candidate offset and call SetHorizontalOffset(Double). After scrolling to the new offset, the notion of 'here' or 'right edge' may have changed because newly de-virtualized content has changed the value of ExtentWidth. Prior to .NET Framework 4.6.2, the scroll operation simply uses the candidate offset, even though it may not be 'here' or at the 'right edge' any more. This results in effects like 'bouncing' the scroll thumb, best illustrated by example. Suppose a DataGrid has ExtentWidth=1000 and Width=200. A scroll to 'Right Edge' uses candidate offset 1000 - 200 = 800. While scrolling to that offset, new columns are de- virtualized; let's suppose they are very wide, so that the ExtentWidth changes to 2000. The scroll ends with HorizontalOffset=800, and the thumb 'bounces' back to near the middle of the scrollbar - precisely at 800/2000 = 40%. The change is to recompute a new candidate offset when this situation occurs, and try again. (This is how vertical scrolling works already.) The change produces a more predictable and intuitive experience for the end user, but it could also affect any app that depends on the exact value of HorizontalOffset after a horizontal scroll, whether invoked by the end user or by an explicit call to SetHorizontalOffset(Double). Xmeye app for computer. |
Suggestion | An app that uses a predicted value for HorizontalOffset should be changed to fetch the actual value (and the value of ExtentWidth) after any horizontal scroll that could change ExtentWidth due to de-virtualization. |
Scope | Minor |
Version | 4.6.2 |
Type | Runtime |
Affected APIs |
Intermittently unable to scroll to bottom item in ItemsControls (like ListBox and DataGrid) when using custom DataTemplates
Details | In some instances, a bug in the .NET Framework 4.5 is causing ItemsControls (like ListBox, ComboBox, DataGrid, etc.) to not scroll to their bottom item when using custom DataTemplates. If the scrolling is attempted a second time (after scrolling back up), it will work then. |
Suggestion | This issue has been fixed in the .NET Framework 4.5.2 and may be addressed by upgrading to that version (or a later version) of the .NET Framework. Alternatively, users can still drag scroll bars to the final items in these collections, but may need to try twice to do so successfully. |
Scope | Minor |
Version | 4.5 |
Type | Runtime |
Items.Clear does not remove duplicates from SelectedItems
Details | Suppose a Selector (with multiple selection enabled) has duplicates in its SelectedItems collection - the same item appears more than once. Removing those items from the data source (e.g. by calling Items.Clear) fails to remove them from SelectedItems; only the first instance is removed. Furthermore, subsequent use of SelectedItems (e.g. SelectedItems.Clear()) can encounter problems such as ArgumentException, because SelectedItems contains items that are no longer in the data source. |
Suggestion | Upgrade if possible to .NET Framework 4.6.2. |
Scope | Minor |
Version | 4.5 |
Type | Runtime |
Affected APIs |
Keytips behavior improved in WPF
Details | Keytips behavior has been modified to bring parity with behavior on Microsoft Word and Windows Explorer. By checking whether keytip state is enabled or not in the case of a SystemKey (in particular, Key or F11) being pressed, WPF handles keytip keys appropriately. Keytips now dismiss a menu even when it is opened by mouse. |
Suggestion | N/A |
Scope | Edge |
Version | 4.7.2 |
Type | Runtime |
ListBoxItem IsSelected binding issue with ObservableCollection<T>.Move
Details | Calling Move(Int32, Int32) or MoveItem(Int32, Int32) on a collection bound to a ListBox with items selected can lead to erratic behavior with future selection or unselection of ListBox items. |
Suggestion | Calling Remove(T) and Insert(Int32, T) instead of Move(Int32, Int32) will work around this issue. Alternatively, this issue has been fixed in the .NET Framework 4.6 and may be addressed by upgrading to that version of the .NET Framework. |
Scope | Minor |
Version | 4.5 |
Type | Runtime |
Affected APIs |
Right clicking on a WPF DataGrid row header changes the DataGrid selection
Download Net Framework 4.5.1 For Windows 7
Details | Right-clicking a selected DataGrid row header while multiple rows are selected results in the DataGrid's selection changing to only that row. |
Suggestion | This issue has been fixed in the .NET Framework 4.6 and may be addressed by upgrading to that version of the .NET Framework. |
Scope | Edge |
Version | 4.5 |
Type | Runtime |
Affected APIs |
WPF Printing Stack Update
Details | WPF's Printing APIs using PrintQueue now call Window's Print Document Package API in favor of the now deprecated XPS Print API. The change was made with serviceability in mind; neither users nor developers should see any changes in behavior or API usage. The new printing stack is enabled by default when running in Windows 10 Creators Update. The old printing stack will still continue to work just as before in older Windows versions. |
Suggestion | To use the old stack in Windows 10 Creators Update, set the UseXpsOMPrinting REG_DWORD value of the HKEY_CURRENT_USERSoftwareMicrosoft.NETFrameworkWindows Presentation FoundationPrinting registry key to 1 . |
Scope | Edge |
Version | 4.7 |
Type | Runtime |
WPF spell checking in text-enabled controls will not work in Windows 10 for languages not in the OS's input language list
Details | When running on Windows 10, the spell checker may not work for WPF text-enabled controls because platform spell-checking capabilities are available only for languages present in the input languages list.In Windows 10, when a language is added to the list of available keyboards, Windows automatically downloads and installs a corresponding Feature on Demand (FOD) package that provides spell-checking capabilities. By adding the language to the input languages list, the spell checker will be supported. |
Suggestion | Be aware that the language or text to be spell-checked must be added as an input language for spell-checking to work in Windows 10. |
Scope | Edge |
Version | 4.6 |
Type | Runtime |
WPF windows are rendered without clipping when extending outside a single monitor
Details | In the .NET Framework 4.6 running on Windows 8 and above, the entire window is rendered without clipping when it extends outside of single display in a multi-monitor scenario. This is different from previous versions of the .NET Framework which would clip WPF windows that extended beyond a single display. |
Suggestion | This behavior (whether to clip or not) can be explicitly set using the <EnableMultiMonitorDisplayClipping> element in <appSettings> in an application's configuration file, or by setting the EnableMultiMonitorDisplayClipping property at app startup. |
Scope | Minor |
Version | 4.6 |
Type | Runtime |
Net Framework 4.5 1 Deutsch Download For Windows 7
Windows Workflow Foundation (WF)
Workflow now throws original exception instead of NullReferenceException in some cases
.net Framework 4.5.1 Download Windows 7
Details | In the .NET Framework 4.6.2 and earlier versions, when the Execute method of a workflow activity throws an exception with a null value for the Message property, the System.Activities Workflow runtime throws a NullReferenceException, masking the original exception.In the .NET Framework 4.7, the previously masked exception is thrown. |
Suggestion | If your code relies on handling the NullReferenceException, change it to catch the exceptions that could be thrown from your custom activities. |
Scope | Minor |
Version | 4.7 |
Type | Runtime |
Affected APIs |
Workflow SQL persistence adds primary key clusters and disallows null values in some columns
Details | Starting with the .NET Framework 4.7, the tables created for the SQL Workflow Instance Store (SWIS) by the SqlWorkflowInstanceStoreSchema.sql script use clustered primary keys. Because of this, identities do not support null values. The operation of SWIS is not impacted by this change. The updates were made to support SQL Server Transactional Replication. |
Suggestion | The SQL file SqlWorkflowInstanceStoreSchemaUpgrade.sql must be applied to existing installations in order to experience this change. New database installations will automatically have the change. |
Scope | Edge |
Version | 4.7 |
Type | Runtime |