From a6ede26927a4c87a0872e7cbc83bed0ec6856527 Mon Sep 17 00:00:00 2001 From: Ron Petrusha Date: Tue, 20 Feb 2018 10:29:52 -0800 Subject: [PATCH] Assorted changes (#625) * Assorted changes * Removed remaining occurences of 'en-us' --- Documentation/compatibility/! Template.md | 4 ++-- ...-SignedXML-and-SignedCMS-default-algorithms-to-SHA256.md | 4 ++-- .../SignedXml.GetPublicKey-returns-RSACng-on-net462.md | 2 +- ...nt-implementations-of-imessagefilter_prefiltermessage.md | 2 +- ...apes-spaces-in-strings-passed-in-via-route-parameters.md | 4 +--- ...as-'selecteditem')-to-a-static-property-does-not-work.md | 2 +- .../compatibility/certificate-eku-oid-validation.md | 2 +- .../change-in-path-separator-character-in-zip-files.md | 2 +- ...ol-blocking-period-for-azure-sql-databases-is-removed.md | 2 +- ...pparameters_parentwindowhandle-now-expects-hwnd-value.md | 2 +- .../compatibility/currentculture-flows-across-tasks.md | 4 ++-- ...ulture-not-preserved-across-wpf-dispatcher-operations.md | 2 +- ...deserialization-of-objects-across-appdomains-can-fail.md | 2 +- ...ng_tasks_task-no-longer-propagate-on-finalizer-thread.md | 2 +- ..._extent-return-different-values-beginning-in-_net-4_5.md | 2 +- .../httprequest_contentencoding-property-prohibits-utf7.md | 2 +- .../httputility_javascriptstringencode-escapes-ampersand.md | 2 +- ...selected-binding-issue-with-observablecollection_move.md | 2 +- ...d-marshal_ptrtostructure-overloads-break-dynamic-code.md | 4 ++-- .../no-longer-able-to-set-enableviewstatemac-to-false.md | 2 +- ...eattribute-and-deprecatedattribute-in-winmd-scenarios.md | 4 ++-- .../remove-ssl3-from-the-wcf-transportdefaults.md | 4 ++-- ...otocol-defaults-to-securityprotocoltype.systemdefault.md | 2 +- ...n-the-web-farm-to-use-the-same-_net-framework-version.md | 2 +- ...to-sql-server-1997-or-databases-using-the-via-adapter.md | 4 ++-- .../compatibility/sslstream-support-for-tls-alerts.md | 2 +- ...5_x_x-version-when-registering-itself-in-the-registry.md | 2 +- ...h-send-aux-record-flag-to-the-underlying-schannel-api.md | 4 ++-- ..._htmldecode-no-longer-decodes-invalid-input-sequences.md | 2 +- .../compatibility/winforms-accessibility-changes-471.md | 6 +++--- .../wpf-layout-rounding-of-margins-has-changed.md | 2 +- ...rtificateclaimset_findclaims-considers-all-claimtypes.md | 2 +- 32 files changed, 42 insertions(+), 44 deletions(-) diff --git a/Documentation/compatibility/! Template.md b/Documentation/compatibility/! Template.md index 5b0354868..7afbd4656 100644 --- a/Documentation/compatibility/! Template.md +++ b/Documentation/compatibility/! Template.md @@ -6,7 +6,7 @@ ### Scope [|Major|Minor|Edge|Transparent|] -//A description of the Scope values can be found at https://docs.microsoft.com/en-us/dotnet/articles/framework/migration-guide/net-compatibility-diagnostics +//A description of the Scope values can be found at https://docs.microsoft.com/dotnet/articles/framework/migration-guide/net-compatibility-diagnostics ### Version Introduced [|Version in which the breaking change first occurred|] @@ -39,7 +39,7 @@ [| List of APIs affected by change referred to using docids|] // For details on how to generate docids, please look at other change files or -// see https://msdn.microsoft.com/en-us/library/fsbx0t7x.aspx for the spec. +// see https://msdn.microsoft.com/library/fsbx0t7x.aspx for the spec. // // For example, if all members of System.Xml.XmlTextReader is affected, we would have the following item: // * `T:System.Xml.XmlTextReader` diff --git a/Documentation/compatibility/Change-SignedXML-and-SignedCMS-default-algorithms-to-SHA256.md b/Documentation/compatibility/Change-SignedXML-and-SignedCMS-default-algorithms-to-SHA256.md index 019447523..76ad8dd4e 100644 --- a/Documentation/compatibility/Change-SignedXML-and-SignedCMS-default-algorithms-to-SHA256.md +++ b/Documentation/compatibility/Change-SignedXML-and-SignedCMS-default-algorithms-to-SHA256.md @@ -24,13 +24,13 @@ There are two new context switch values to control whether SHA1 (insecure) or SH - Switch.System.Security.Cryptography.Pkcs.UseInsecureHashAlgorithms -For applications that target the .NET Framework 4.7.1 and later versions, if the use of SHA256 is undesirable, you can restore the default to SHA1 by adding the following configuration switch to the [runtime](https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/runtime-element) section of your app config file: +For applications that target the .NET Framework 4.7.1 and later versions, if the use of SHA256 is undesirable, you can restore the default to SHA1 by adding the following configuration switch to the [runtime](~/docs/framework/configure-apps/file-schema/runtime/runtime-element.md) section of your app config file: ```xml ``` -For applications that target the .NET Framework 4.7 and earlier versions, you can opt into this change by adding the following configuration switch to the [runtime](https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/runtime-element) section of your app config file: +For applications that target the .NET Framework 4.7 and earlier versions, you can opt into this change by adding the following configuration switch to the [runtime](~/docs/framework/configure-apps/file-schema/runtime/runtime-element.md) section of your app config file: ```xml diff --git a/Documentation/compatibility/SignedXml.GetPublicKey-returns-RSACng-on-net462.md b/Documentation/compatibility/SignedXml.GetPublicKey-returns-RSACng-on-net462.md index a892a3723..f71f70bb3 100644 --- a/Documentation/compatibility/SignedXml.GetPublicKey-returns-RSACng-on-net462.md +++ b/Documentation/compatibility/SignedXml.GetPublicKey-returns-RSACng-on-net462.md @@ -21,7 +21,7 @@ Starting with the .NET Framework 4.6.2, the concrete type of the object returned ### Recommended Action -Starting with apps running on the .NET Framework 4.7.1, you can use the CryptoServiceProvider implementation used by default in the .NET Framework 4.6.1 and earlier versions by adding the following configuration switch to the [runtime](https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/runtime-element) section of your app config file: +Starting with apps running on the .NET Framework 4.7.1, you can use the CryptoServiceProvider implementation used by default in the .NET Framework 4.6.1 and earlier versions by adding the following configuration switch to the [runtime](~/docs/framework/configure-apps/file-schema/runtime/runtime-element.md) section of your app config file: ```xml diff --git a/Documentation/compatibility/application_filtermessage-no-longer-throws-for-re-entrant-implementations-of-imessagefilter_prefiltermessage.md b/Documentation/compatibility/application_filtermessage-no-longer-throws-for-re-entrant-implementations-of-imessagefilter_prefiltermessage.md index abef1e5ad..82da4feab 100644 --- a/Documentation/compatibility/application_filtermessage-no-longer-throws-for-re-entrant-implementations-of-imessagefilter_prefiltermessage.md +++ b/Documentation/compatibility/application_filtermessage-no-longer-throws-for-re-entrant-implementations-of-imessagefilter_prefiltermessage.md @@ -38,7 +38,7 @@ Framework 4.6.1. Apps targeting the .NET Framework 4.6.1 can opt out of this change (or apps targeting older Frameworks may opt in) by using the -[DontSupportReentrantFilterMessage](https://docs.microsoft.com/en-us/dotnet/articles/framework/migration-guide/mitigation-custom-imessagefilter-prefiltermessage-implementations#mitigation) +[DontSupportReentrantFilterMessage](~/docs/framework/migration-guide/mitigation-custom-imessagefilter-prefiltermessage-implementations#mitigation.md) compatibility switch. ### Affected APIs diff --git a/Documentation/compatibility/asp_net-mvc-now-escapes-spaces-in-strings-passed-in-via-route-parameters.md b/Documentation/compatibility/asp_net-mvc-now-escapes-spaces-in-strings-passed-in-via-route-parameters.md index 158bace05..5f58a9092 100644 --- a/Documentation/compatibility/asp_net-mvc-now-escapes-spaces-in-strings-passed-in-via-route-parameters.md +++ b/Documentation/compatibility/asp_net-mvc-now-escapes-spaces-in-strings-passed-in-via-route-parameters.md @@ -19,13 +19,11 @@ In order to conform to RFC 2396, spaces in route paths are now escaped when popu Code should be updated to unescape string parameters from a route. If the original URI is needed, it can be accessed with the .OriginalString API. ### Affected APIs -* `M:System.Web.Http.RouteAttribute.%23ctor(System.String)` +* `M:System.Web.Mvc.RouteAttribute.#ctor(System.String)` ### Category ASP.NET -[More information](http://connect.microsoft.com/VisualStudio/feedback/details/878827/issues-with-encoding-in-web-api-in-4-5-2) - diff --git a/Documentation/compatibility/currentculture-not-preserved-across-wpf-dispatcher-operations.md b/Documentation/compatibility/currentculture-not-preserved-across-wpf-dispatcher-operations.md index da136b19f..30fb36682 100644 --- a/Documentation/compatibility/currentculture-not-preserved-across-wpf-dispatcher-operations.md +++ b/Documentation/compatibility/currentculture-not-preserved-across-wpf-dispatcher-operations.md @@ -67,7 +67,7 @@ setting the following compatibility switch: ``` This issue has been fixed by WPF in .NET Framework 4.6.2. It has also been fixed -in .NET Frameworks 4.6, 4.6.1 through [KB 3139549](https://support.microsoft.com/en-us/kb/3139549). +in .NET Frameworks 4.6, 4.6.1 through [KB 3139549](https://support.microsoft.com/kb/3139549). Applications targeting .NET 4.6 or later will automatically get the right behavior in WPF applications - /) diff --git a/Documentation/compatibility/deserialization-of-objects-across-appdomains-can-fail.md b/Documentation/compatibility/deserialization-of-objects-across-appdomains-can-fail.md index 6ca5ff3fc..770f48d77 100644 --- a/Documentation/compatibility/deserialization-of-objects-across-appdomains-can-fail.md +++ b/Documentation/compatibility/deserialization-of-objects-across-appdomains-can-fail.md @@ -16,7 +16,7 @@ In some cases, when an app uses two or more app domains with different applicati - [ ] Build-time break ### Recommended Action -See [Mitigation: Deserialization of Objects Across App Domains](https://docs.microsoft.com/en-us/dotnet/articles/framework/migration-guide/mitigation-deserialization-of-objects-across-app-domains) +See [Mitigation: Deserialization of Objects Across App Domains](~/docs/framework/migration-guide/mitigation-deserialization-of-objects-across-app-domains.md) ### Affected APIs * Not detectable via API analysis diff --git a/Documentation/compatibility/exceptions-during-unobserved-processing-in-system_threading_tasks_task-no-longer-propagate-on-finalizer-thread.md b/Documentation/compatibility/exceptions-during-unobserved-processing-in-system_threading_tasks_task-no-longer-propagate-on-finalizer-thread.md index 54b0c6758..918b4fa17 100644 --- a/Documentation/compatibility/exceptions-during-unobserved-processing-in-system_threading_tasks_task-no-longer-propagate-on-finalizer-thread.md +++ b/Documentation/compatibility/exceptions-during-unobserved-processing-in-system_threading_tasks_task-no-longer-propagate-on-finalizer-thread.md @@ -29,7 +29,7 @@ finalizer thread, the previous behavior can be restored by providing an appropriate handler for the event, or by setting a -[runtime configuration element](https://docs.microsoft.com/en-us/dotnet/articles/framework/configure-apps/file-schema/runtime/throwunobservedtaskexceptions-element). +[runtime configuration element](~/docs/framework/configure-apps/file-schema/runtime/throwunobservedtaskexceptions-element.md). ### Affected APIs * `M:System.Threading.Tasks.Task.Run(System.Action)` diff --git a/Documentation/compatibility/glyphrun_computeinkboundingbox()-and-formattedtext_extent-return-different-values-beginning-in-_net-4_5.md b/Documentation/compatibility/glyphrun_computeinkboundingbox()-and-formattedtext_extent-return-different-values-beginning-in-_net-4_5.md index acc51e8d7..39f391395 100644 --- a/Documentation/compatibility/glyphrun_computeinkboundingbox()-and-formattedtext_extent-return-different-values-beginning-in-_net-4_5.md +++ b/Documentation/compatibility/glyphrun_computeinkboundingbox()-and-formattedtext_extent-return-different-values-beginning-in-_net-4_5.md @@ -43,6 +43,6 @@ the app.config file: ### Category Windows Presentation Foundation (WPF) -[More information](http://support.microsoft.com/en-us/kb/3009678) +[More information](http://support.microsoft.com/kb/3009678) diff --git a/Documentation/compatibility/httprequest_contentencoding-property-prohibits-utf7.md b/Documentation/compatibility/httprequest_contentencoding-property-prohibits-utf7.md index 803711149..254c93763 100644 --- a/Documentation/compatibility/httprequest_contentencoding-property-prohibits-utf7.md +++ b/Documentation/compatibility/httprequest_contentencoding-property-prohibits-utf7.md @@ -25,7 +25,7 @@ Ideally, applications should be updated to not use UTF-7 encoding in s. Alternatively, legacy behavior can be restored by using the `aspnet:AllowUtf7RequestContentEncoding` attribute of the -[appSettings](https://msdn.microsoft.com/en-us/library/hh975440(v=vs.110).aspx) +[appSettings](https://msdn.microsoft.com/library/hh975440(v=vs.110).aspx) element. ### Affected APIs diff --git a/Documentation/compatibility/httputility_javascriptstringencode-escapes-ampersand.md b/Documentation/compatibility/httputility_javascriptstringencode-escapes-ampersand.md index 789a87fa1..b851ba4da 100644 --- a/Documentation/compatibility/httputility_javascriptstringencode-escapes-ampersand.md +++ b/Documentation/compatibility/httputility_javascriptstringencode-escapes-ampersand.md @@ -21,7 +21,7 @@ escapes the ampersand (&) character. If your app depends on the previous behavior of this method, you can add an aspnet:JavaScriptDoNotEncodeAmpersand setting to the -[ASP.NET appSettings element](https://msdn.microsoft.com/en-us/library/hh975440(v=vs.110).aspx) +[ASP.NET appSettings element](https://msdn.microsoft.com/library/hh975440.aspx) in your configuration file. ### Affected APIs diff --git a/Documentation/compatibility/listboxitem-isselected-binding-issue-with-observablecollection_move.md b/Documentation/compatibility/listboxitem-isselected-binding-issue-with-observablecollection_move.md index 25321ae61..ebbe37bbb 100644 --- a/Documentation/compatibility/listboxitem-isselected-binding-issue-with-observablecollection_move.md +++ b/Documentation/compatibility/listboxitem-isselected-binding-issue-with-observablecollection_move.md @@ -43,6 +43,6 @@ Framework. ### Category Windows Presentation Foundation (WPF) -[More information](http://social.msdn.microsoft.com/Forums/en-US/afcbc8b3-a2f2-41e4-b402-2efc9eab1ffe/listboxitem-isselected-binding-issue-with-observablecollectiontmove?forum=wpf) +[More information](http://social.msdn.microsoft.com/Forums/afcbc8b3-a2f2-41e4-b402-2efc9eab1ffe/listboxitem-isselected-binding-issue-with-observablecollectiontmove?forum=wpf) diff --git a/Documentation/compatibility/marshal_sizeof-and-marshal_ptrtostructure-overloads-break-dynamic-code.md b/Documentation/compatibility/marshal_sizeof-and-marshal_ptrtostructure-overloads-break-dynamic-code.md index 797260b3f..724684164 100644 --- a/Documentation/compatibility/marshal_sizeof-and-marshal_ptrtostructure-overloads-break-dynamic-code.md +++ b/Documentation/compatibility/marshal_sizeof-and-marshal_ptrtostructure-overloads-break-dynamic-code.md @@ -29,7 +29,7 @@ have been added that may be ambiguous to the scripting engines. Update scripts to clearly indicate which overload should be used. This can typically done by explicitly casting the methods' type parameters as -. See [this link](https://support.microsoft.com/en-us/kb/2909958/) +. See [this link](https://support.microsoft.com/kb/2909958/) for more detail and examples of how to workaround the issue. ### Affected APIs @@ -38,7 +38,7 @@ for more detail and examples of how to workaround the issue. ### Category Core -[More information](https://support.microsoft.com/en-us/kb/2909958/) +[More information](https://support.microsoft.com/kb/2909958/) diff --git a/Documentation/compatibility/sqlconnection-can-no-longer-connect-to-sql-server-1997-or-databases-using-the-via-adapter.md b/Documentation/compatibility/sqlconnection-can-no-longer-connect-to-sql-server-1997-or-databases-using-the-via-adapter.md index e53181db2..1c803fefe 100644 --- a/Documentation/compatibility/sqlconnection-can-no-longer-connect-to-sql-server-1997-or-databases-using-the-via-adapter.md +++ b/Documentation/compatibility/sqlconnection-can-no-longer-connect-to-sql-server-1997-or-databases-using-the-via-adapter.md @@ -10,7 +10,7 @@ Edge Planned ### Change Description -Connections to SQL Server databases using the [Virtual Interface Adapter (VIA) protocol](https://technet.microsoft.com/en-us/library/ms191229%28v=sql.105%29.aspx) are no longer supported. +Connections to SQL Server databases using the [Virtual Interface Adapter (VIA) protocol](https://technet.microsoft.com/library/ms191229%28v=sql.105%29.aspx) are no longer supported. The protocol used to connect to a SQL Server database is visible in the connection string. A VIA connection will contain via:\. If this app is connecting to SQL via a protocol other than VIA (tcp: or np: for example), then no breaking change will be encountered. @@ -20,7 +20,7 @@ Also, connections to SQL Server 7 (1997) are no longer supported. - [ ] Build-time break ### Recommended Action -The VIA protocol is deprecated, so an alternative protocol should be used to connect to SQL databases. The most common protocol used is TCP/IP. Instructions for enabling the TCP/IP protocol can be found [here](https://msdn.microsoft.com/en-us/library/bb909712(v=vs.120).aspx). If the database is only accessed from within an intranet, the shared pipes protocol may provide better performance if the network is slow. +The VIA protocol is deprecated, so an alternative protocol should be used to connect to SQL databases. The most common protocol used is TCP/IP. Instructions for enabling the TCP/IP protocol can be found [here](https://msdn.microsoft.com/library/bb909712.aspx). If the database is only accessed from within an intranet, the shared pipes protocol may provide better performance if the network is slow. ### Affected APIs * `M:System.Data.SqlClient.SqlConnection.#ctor(System.String)` diff --git a/Documentation/compatibility/sslstream-support-for-tls-alerts.md b/Documentation/compatibility/sslstream-support-for-tls-alerts.md index b311132ec..d6be2a543 100644 --- a/Documentation/compatibility/sslstream-support-for-tls-alerts.md +++ b/Documentation/compatibility/sslstream-support-for-tls-alerts.md @@ -18,7 +18,7 @@ be thrown by the first I/O Read/Write operation. The code for the can be mapped to the TLS Alert from the remote party using this -[Schannel documentation](https://msdn.microsoft.com/en-us/library/windows/desktop/dd721886%28v=vs.85%29.aspx). +[Schannel documentation](https://msdn.microsoft.com/library/windows/desktop/dd721886%28v=vs.85%29.aspx). For more information, see [RFC 2246: Section 7.2.2 Error alerts](https://tools.ietf.org/html/rfc2246#section-7.2.2) diff --git a/Documentation/compatibility/the-_net-framework-4_6-does-not-use-a-4_5_x_x-version-when-registering-itself-in-the-registry.md b/Documentation/compatibility/the-_net-framework-4_6-does-not-use-a-4_5_x_x-version-when-registering-itself-in-the-registry.md index 6fec39a19..d63f0871f 100644 --- a/Documentation/compatibility/the-_net-framework-4_6-does-not-use-a-4_5_x_x-version-when-registering-itself-in-the-registry.md +++ b/Documentation/compatibility/the-_net-framework-4_6-does-not-use-a-4_5_x_x-version-when-registering-itself-in-the-registry.md @@ -24,6 +24,6 @@ Update apps probing for a .NET Framework 4.5 install by looking for 4.5 registry ### Category Setup and Deployment -[More information](https://docs.microsoft.com/en-us/dotnet/articles/framework/migration-guide/mitigation-product-versioning) +[More information](~/docs/framework/migration-guide/mitigation-product-versioning.md) diff --git a/Documentation/compatibility/tls-1-x-by-default-passes-sch-send-aux-record-flag-to-the-underlying-schannel-api.md b/Documentation/compatibility/tls-1-x-by-default-passes-sch-send-aux-record-flag-to-the-underlying-schannel-api.md index 6746d9280..08eeb1b3c 100644 --- a/Documentation/compatibility/tls-1-x-by-default-passes-sch-send-aux-record-flag-to-the-underlying-schannel-api.md +++ b/Documentation/compatibility/tls-1-x-by-default-passes-sch-send-aux-record-flag-to-the-underlying-schannel-api.md @@ -11,7 +11,7 @@ NotPlanned ### Change Description -When using TLS 1.x, the .NET Framework relies on the underlying Windows SCHANNEL API. Starting with .NET Framework 4.6, the [`SCH_SEND_AUX_RECORD`](https://msdn.microsoft.com/en-us/library/windows/desktop/aa379810(v=vs.85).aspx) flag is passed by default to SCHANNEL. This causes SCHANNEL to split data to be encrypted into two separate records, the first as a single byte and the second as *n*-1 bytes. +When using TLS 1.x, the .NET Framework relies on the underlying Windows SCHANNEL API. Starting with .NET Framework 4.6, the [`SCH_SEND_AUX_RECORD`](https://msdn.microsoft.com/library/windows/desktop/aa379810.aspx) flag is passed by default to SCHANNEL. This causes SCHANNEL to split data to be encrypted into two separate records, the first as a single byte and the second as *n*-1 bytes. In rare cases, this breaks communication between clients and existing servers that make the assumption that the data resides in a single record. @@ -20,7 +20,7 @@ In rare cases, this breaks communication between clients and existing servers th ### Recommended Action -If this change breaks communication with an existing server, you can disable sending the [`SCH_SEND_AUX_RECORD`](https://msdn.microsoft.com/en-us/library/windows/desktop/aa379810(v=vs.85).aspx) flag and restore the previous behavior of not splitting data into separate records by adding the following switch to the [`\` element](https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/appcontextswitchoverrides-element) in the [`\ section](https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/runtime-element) of your app configuration file: +If this change breaks communication with an existing server, you can disable sending the [`SCH_SEND_AUX_RECORD`](https://msdn.microsoft.com/library/windows/desktop/aa379810.aspx) flag and restore the previous behavior of not splitting data into separate records by adding the following switch to the [`\` element](~/docs/framework/configure-apps/file-schema/runtime/appcontextswitchoverrides-element.md) in the [`\ section](~/docs/framework/configure-apps/file-schema/runtime/runtime-element.md) of your app configuration file: ```xml diff --git a/Documentation/compatibility/webutility_htmldecode-no-longer-decodes-invalid-input-sequences.md b/Documentation/compatibility/webutility_htmldecode-no-longer-decodes-invalid-input-sequences.md index 7ee29d7be..8d1daf250 100644 --- a/Documentation/compatibility/webutility_htmldecode-no-longer-decodes-invalid-input-sequences.md +++ b/Documentation/compatibility/webutility_htmldecode-no-longer-decodes-invalid-input-sequences.md @@ -16,7 +16,7 @@ By default, decoding methods no longer decode an invalid input sequence into an - [ ] Build-time break ### Recommended Action -The change in decoder output should matter only if you store binary data instead of UTF-16 data in strings. To explicitly control this behavior, set the `aspnet:AllowRelaxedUnicodeDecoding` attribute of the [appSettings](https://msdn.microsoft.com/en-us/library/ms228154(v=vs.110).aspx) element to true to enable legacy behavior or to false to enable the current behavior. +The change in decoder output should matter only if you store binary data instead of UTF-16 data in strings. To explicitly control this behavior, set the `aspnet:AllowRelaxedUnicodeDecoding` attribute of the [appSettings](~/docs/framework/configure-apps/file-schema/appsettings.md) element to `true` to enable legacy behavior or to `false` to enable the current behavior. ### Affected APIs * `M:System.Net.WebUtility.HtmlDecode(System.String)` diff --git a/Documentation/compatibility/winforms-accessibility-changes-471.md b/Documentation/compatibility/winforms-accessibility-changes-471.md index 1732e3682..5d4226aa7 100644 --- a/Documentation/compatibility/winforms-accessibility-changes-471.md +++ b/Documentation/compatibility/winforms-accessibility-changes-471.md @@ -51,7 +51,7 @@ For an overview of UI automation, see the [UI Automation Overview](https://docs. **Added support for UI Automation patterns and properties** -Accessibility clients can take advantage of new WinForms accessibility functionality by using common, publicly described invocation patterns. These patterns are not WinForms-specific. For instance, accessibility clients can call the QueryInterface method on the IAccessible interface (MAAS) to obtain an IServiceProvider interface. If this interface is available, clients can use its QueryService method to request an IAccessibleEx interface. For more information, see [Using IAccessibleEx from a Client](https://msdn.microsoft.com/en-us/library/windows/desktop/dd561924(v=vs.85).aspx). Starting with the .NET Framework 4.7.1, IServiceProvider and [IAccessibleEx]( https://msdn.microsoft.com/en-us/library/windows/desktop/dd561898(v=vs.85).aspx) (where applicable) are available for WinForms accessibility objects. +Accessibility clients can take advantage of new WinForms accessibility functionality by using common, publicly described invocation patterns. These patterns are not WinForms-specific. For instance, accessibility clients can call the QueryInterface method on the IAccessible interface (MAAS) to obtain an IServiceProvider interface. If this interface is available, clients can use its QueryService method to request an IAccessibleEx interface. For more information, see [Using IAccessibleEx from a Client](https://msdn.microsoft.com/library/windows/desktop/dd561924.aspx). Starting with the .NET Framework 4.7.1, IServiceProvider and [IAccessibleEx]( https://msdn.microsoft.com/library/windows/desktop/dd561898.aspx) (where applicable) are available for WinForms accessibility objects. The .NET Framework 4.7.1 adds support for the following UI automation patterns and properties: @@ -102,14 +102,14 @@ NOTE: Windows10 has changed values for some high contrast system colors. Windows - The `T:System.Windows.Forms.CheckedListBox` control now notifies Narrator when the `P:System.Windows.Forms.CheckState` property has been changed. Previously, Narrator did not recieve notification and as a result users would not be informed that the `P:System.Windows.Forms.CheckState` had been updated. - The `T:System.Windows.Forms.LinkLabel` control has changed the way it notifies Narrator of the text of in the control. Previously, Narrator announced this text twice and read "&" symbols as real text even though they are not visible to a user. The duplicated text was removed from the Narrator announcements, as well as unnecessary "&" symbols. - The `T:System.Windows.Forms.DataGridViewCell` control types now correctly report the read-only status to Narrator and other assistive technologies. -- Narrator is now able to read the System Menu of child windows in [Multiple-Document Interface](https://docs.microsoft.com/en-us/dotnet/framework/winforms/advanced/multiple-document-interface-mdi-applications) applications. +- Narrator is now able to read the System Menu of child windows in [Multiple-Document Interface]~/docs/framework/winforms/advanced/multiple-document-interface-mdi-applications.md) applications. - Narrator is now able to read `T:System.Windows.Forms.ToolStripMenuItem` controls with a `P:System.Windows.Forms.ToolStripItem.Enabled` property set to _false_. Previously, Narrator was unable to focus on disabled menu items to read hte content. ### Affected APIs * `M:System.Windows.Forms.ToolStripDropDownButton.CreateAccessibilityInstance` * `P:System.Windows.Forms.DomainUpDown.DomainUpDownAccessibleObject.Name` -* `T:System.Windows.Forms.MonthCalendar.AccessibilityObject` +* [MonthCalendar.AccessibilityObject](xref:System.Windows.Forms.Control.AccessibilityObject) ### Category diff --git a/Documentation/compatibility/wpf-layout-rounding-of-margins-has-changed.md b/Documentation/compatibility/wpf-layout-rounding-of-margins-has-changed.md index f2351a6d6..dff018e26 100644 --- a/Documentation/compatibility/wpf-layout-rounding-of-margins-has-changed.md +++ b/Documentation/compatibility/wpf-layout-rounding-of-margins-has-changed.md @@ -32,6 +32,6 @@ Apps that target the .NET Framework 4.6 but want WPF controls to render using th ### Category Windows Presentation Foundation (WPF) -[More information](https://docs.microsoft.com/en-us/dotnet/articles/framework/migration-guide/mitigation-wpf-layout) +[More information](~/docs/framework/migration-guide/mitigation-wpf-layout.md) diff --git a/Documentation/compatibility/x509certificateclaimset_findclaims-considers-all-claimtypes.md b/Documentation/compatibility/x509certificateclaimset_findclaims-considers-all-claimtypes.md index 938932a01..29e65c46d 100644 --- a/Documentation/compatibility/x509certificateclaimset_findclaims-considers-all-claimtypes.md +++ b/Documentation/compatibility/x509certificateclaimset_findclaims-considers-all-claimtypes.md @@ -27,7 +27,7 @@ method attempts to match the claimType argument only with the last DNS entry. This change only affects applications targeting the .NET Framework 4.6.1. This change may be disabled (or enabled if targetting pre-4.6.1) with the -[DisableMultipleDNSEntries](https://docs.microsoft.com/en-us/dotnet/articles/framework/migration-guide/mitigation-x509certificateclaimset-findclaims-method#mitigation) +[DisableMultipleDNSEntries](~/docs/framework/migration-guide/mitigation-x509certificateclaimset-findclaims-method#mitigation.md) compatibility switch. ### Affected APIs