diff --git a/Documentation/compatibility/ServiceBase-doesnt-propagate-OnStart-exceptions.md b/Documentation/compatibility/ServiceBase-doesnt-propagate-OnStart-exceptions.md index 90dadd9..0b45c0a 100644 --- a/Documentation/compatibility/ServiceBase-doesnt-propagate-OnStart-exceptions.md +++ b/Documentation/compatibility/ServiceBase-doesnt-propagate-OnStart-exceptions.md @@ -36,4 +36,8 @@ If your application targets an earlier version than 4.7.1 but you want to have t ``` ### Affected APIs -* `M:System.ServiceProcess.ServiceBase.Run` +* `M:System.ServiceProcess.ServiceBase.Run(System.ServiceProcess.ServiceBase)` +* `M:System.ServiceProcess.ServiceBase.Run(System.ServiceProcess.ServiceBase[])` + +### Category +Core \ No newline at end of file diff --git a/Documentation/compatibility/WCFSDKToolsAccessibilityChangesIn4.7.1 b/Documentation/compatibility/WCFSDKToolsAccessibilityChangesIn4.7.1 deleted file mode 100644 index aa4905d..0000000 --- a/Documentation/compatibility/WCFSDKToolsAccessibilityChangesIn4.7.1 +++ /dev/null @@ -1,23 +0,0 @@ -##Improved accessibility for some .NET SDK tools - -###Scope -Edge -###Version Introduced -.NET Framework 4.7.1 -###Source Analyzer Status -NotPlanned -###Change Description -In .NET Framework SDK 4.7.1, svcconfigedit.exe and svctraceviewer.exe tools have been improved by fixing varied accessibility issues. Most of these were small issues like a name not being defined or certain UI Automation patterns not being implemented correctly. While many users wouldn’t be aware of these incorrect values, for customers who use assistive technologies like screen readers, they will find these SDK tools become more accessible. Certainly, these fixes change some previous behaviors, like keyboard focus order. -###Quirked: -In order to get all the accessibility fixes in these tools, you can add App config file with the following configuration: - - - -###Affected APIs -* Not detectable via API analysis - - diff --git a/Documentation/compatibility/WCFSDKToolsAccessibilityChangesIn4.7.1.md b/Documentation/compatibility/WCFSDKToolsAccessibilityChangesIn4.7.1.md new file mode 100644 index 0000000..e067966 --- /dev/null +++ b/Documentation/compatibility/WCFSDKToolsAccessibilityChangesIn4.7.1.md @@ -0,0 +1,35 @@ +## Improved accessibility for some .NET SDK tools + +### Scope +Edge + +### Version Introduced +4.7.1 + +### Source Analyzer Status +NotPlanned + +### Change Description + +In the .NET Framework SDK 4.7.1, the svcconfigedit.exe and svctraceviewer.exe tools have been improved by fixing varied accessibility issues. Most of these were small issues like a name not being defined or certain UI automation patterns not being implemented correctly. While many users wouldn’t be aware of these incorrect values, customers who use assistive technologies like screen readers will find these SDK tools more accessible. Certainly, these fixes change some previous behaviors, like keyboard focus order. + +In order to get all the accessibility fixes in these tools, you can the following to your app.config file: +```xml + + + +``` + +- [x] Quirked +- [ ] Build-time break + +### Affected APIs +* Not detectable via API analysis + +### Category +Windows Communication Foundation (WCF) + + diff --git a/Documentation/compatibility/wpf-accessibility-improvements.MD b/Documentation/compatibility/wpf-accessibility-improvements.MD index 2b330a4..f52b507 100644 --- a/Documentation/compatibility/wpf-accessibility-improvements.MD +++ b/Documentation/compatibility/wpf-accessibility-improvements.MD @@ -44,7 +44,7 @@ The LiveSetting property also lets the screen reader know how important it is to ### Recommended Action __How to opt in or out of these changes__ - + In order for the application to benefit from these changes, it must run on the .NET Framework 4.7.1 or later. The application can benefit from these changes in either of the following ways: - It is recompiled to target the .NET Framework 4.7.1. These accessibility changes are enabled by default on WPF applications that target the .NET Framework 4.7.1 or later. - It opts out of the legacy accessibility behaviors by adding the following [AppContext Switch](https://docs.microsoft.com/dotnet/framework/configure-apps/file-schema/runtime/appcontextswitchoverrides-element) in the `````` section of the app config file and setting it to false, as the following example shows. @@ -64,14 +64,15 @@ Applications that target the .NET Framework 4.7.1 or later and want to preserve For an overview of UI automation, see the [UI Automation Overview](https://docs.microsoft.com/dotnet/framework/ui-automation/ui-automation-overview). -### Affected APIs -* `F:System.windows.Automation.AutomationElementIdentifiers.LiveSettingProperty` -* `F:System.windows.Automation.AutomationElementIdentifiers.LiveRegionChangedEvent` -* `F:System.Windows.Automation.AutomationProperties.LiveSetting` -* `M:System.Windows.Automation.AutomationProperties.SetLiveSetting` -* `M:System.Windows.Automation.AutomationProperties.GetLiveSetting` -* `M:System.Windows.Automation.Peers.AutomationPeer.GetLiveSettingCore` -* `T:System.Windows.Automation.AutomationLiveSetting` +### Affected APIs +* `F:System.Windows.Automation.AutomationElementIdentifiers.LiveSettingProperty` +* `F:System.Windows.Automation.AutomationElementIdentifiers.LiveRegionChangedEvent` +* `T:System.Windows.Automation.AutomationLiveSetting` +* `F:System.Windows.Automation.AutomationProperties.LiveSettingProperty` +* `M:System.Windows.Automation.AutomationProperties.SetLiveSetting(System.Windows.DependencyObject,System.Windows.Automation.AutomationLiveSetting)` +* `M:System.Windows.Automation.AutomationProperties.GetLiveSetting(System.Windows.DependencyObject)` +* `M:System.Windows.Automation.Peers.AutomationPeer.GetLiveSettingCore` + ### Category @@ -90,7 +91,7 @@ WPF 437421 436104 430176 - + 429415 453792 404634