Runtime Changes for Migration from .NET Framework 4.6.2 to 4.7.2

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:

Major This is a significant change that affects a large number of apps or that requires substantial modification of code.

Minor This is a change that affects a small number of apps or that requires minor modification of code.

Edge case This is a change that affects apps under very specific scenarios that are not common.

Transparent This 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.6.2 to 4.7.2, review the following topics for application compatibility issues that may affect your app:

Core

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:
  • The URI has the scheme file: and is followed by four or more slashes.
  • The host name begins with an underscore or other non-reserved symbol.
  • The URI contains Unicode characters.
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

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:
bool success = Uri.TryCreate("http:%C3%A8", UriKind.RelativeOrAbsolute, out Uri href);
bool success = Uri.TryCreate("http:è", UriKind.RelativeOrAbsolute, out Uri href);
To reproduce the NullReferenceException, the following items must be true:
  • The URI must be specified as relative by prepending it with ‘http:’ and not following it with ‘//’.
  • The URI must contain percent-encoded Unicode or unreserved symbols.
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

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
  • Validate if your server and client certification has the required EKU OID. If not, update your certification.
  • Validate if your root certificate is invalid. If so, update the root certificate.
  • How to opt out of the change: If you can't update the certificate, you can work around the breaking change temporarily with the following configuration setting, However, opting out of the change will leave your system vulnerable to the security issue.
<appSettings>
<add key="wcf:useLegacyCertificateUsagePolicy" value="true" />
</appSettings>
Scope Minor
Version 4.7.2
Type Runtime

Security

RSACng and DSACng are once again usable in Partial Trust scenarios

Details CngLightup (used in several higher-level crypto apis, such as System.Security.Cryptography.Xml.EncryptedXml) and System.Security.Cryptography.RSACng in some cases rely on full trust. These include P/Invokes without asserting SecurityPermissionFlag.UnmanagedCode permissions, and code paths where System.Security.Cryptography.CngKey has permission demands for SecurityPermissionFlag.UnmanagedCode. Starting with the .NET Framework 4.6.2, CngLightup was used to switch to System.Security.Cryptography.RSACng wherever possible. As a result, partial trust apps that successfully used System.Security.Cryptography.Xml.EncryptedXml began to fail and throw SecurityException exceptions.This change adds the required asserts so that all functions using CngLightup have the required permissions.
Suggestion If this change in the .NET Framework 4.6.2 has negatively impacted your partial trust apps, upgrade to the .NET Framework 4.7.1.
Scope Edge
Version 4.6.2
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.
<configuration>
<appsettings>
...
<add key="dataAnnotations:dataTypeAttribute:disableRegEx" value="false"/>
...
</appsettings>
</configuration>
Scope Minor
Version 4.7.2
Type Runtime

Windows Communication Foundation (WCF)

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::
<configuration>
<runtime>
<AppContextSwitchOverrides value="Switch.System.ServiceModel.DisableAddressHeaderCollectionValidation=true" />
</runtime>
</configuration>
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:
<configuration>
<runtime>
<AppContextSwitchOverrides value="Switch.System.ServiceModel.UseSha1InMsmqEncryptionAlgorithm=true" />
</runtime>
</configuration>
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:
<configuration>
<runtime>
<AppContextSwitchOverrides value="Switch.System.ServiceModel.UseSha1InPipeConnectionGetHashAlgorithm=true" />
</runtime>
</configuration>
Scope Minor
Version 4.7.1
Type Runtime

Windows Presentation Foundation (WPF)

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:
  • Open two levels, click outside P2 but inside P1. Nothing happens.
  • Open two levels, click outside P1. Both popups close.
  • Open and close two levels. Then try to open P2 again. Nothing happens.
  • Try to open three levels. You can't. (Either nothing happens or the first two levels close, depending on where you click.) These cases (and other variants) now work as expected.
Scope Edge
Version 4.7.1
Type Runtime
Affected APIs

DataGridCellsPanel.BringIndexIntoView throws ArgumentOutOfRangeException

Details ScrollIntoView(Object) will work asynchronously when column virtualization is enabled but the column widths have not yet been determined. If columns are removed before the asynchronous work happens, an ArgumentOutOfRangeException can occur.
Suggestion Any one of the following:
  1. Upgrade to .NET Framework 4.7.
  2. Install the latest servicing patch for .NET Framework 4.6.2.
  3. Avoid removing columns until the asynchronous response to ScrollIntoView(Object) has completed.
Scope Edge
Version 4.6.2
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

ObjectDisposedException thrown by WPF spellchecker

Details WPF applications occasionally crash during application shutdown with an ObjectDisposedException thrown by the spellchecker. This is fixed in .NET Framework 4.7 WPF by handling the exception gracefully, and thus ensuring that applications are no longer adversely affected. It should be noted that occasional first-chance exceptions would continue to be observed in applications running under a debugger.
Suggestion Upgrade to .NET Framework 4.7
Scope Edge
Version 4.6.1
Type Runtime

RibbonGroup background is set to transparent in localized builds

Details RibbonGroup background on localized builds was always painted with Transparent brush, resulting in poor UI experience. This is fixed in .NET Framework 4.7 WPF fix by updating the localized resources for RibbonGroup, which in turn ensures that the correct brush is selected.
Suggestion Upgrade to .NET Framework 4.7
Scope Edge
Version 4.6.2
Type Runtime

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_USER\Software\Microsoft.NETFramework\Windows Presentation Foundation\Printing registry key to 1.
Scope Edge
Version 4.7
Type Runtime

Windows Workflow Foundation (WF)

Workflow now throws original exception instead of NullReferenceException in some cases

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