daohualiuxiang
/
dotnet
mirror of https://github.com/microsoft/dotnet.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix more issues (#536) 

* Add Category for breaking change

* Fix formatting for breaking change

* Rename to markdown file so it can be parsed

* Add category to WCF change

* Update WCFSDKToolsAccessibilityChangesIn4.7.1.md

* Fix docIds

* Fix broken docIds

* Fix more docIds
pull/539/head
Connie Yau 2017-10-24 15:08:02 -07:00 committed by GitHub
parent 564a679509
commit 289487a694
4 changed files with 51 additions and 34 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Documentation/compatibility/ServiceBase-doesnt-propagate-OnStart-exceptions.md
View File

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

23
Documentation/compatibility/WCFSDKToolsAccessibilityChangesIn4.7.1
View File

@ -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:
<runtime>
<AppContextSwitchOverrides value="Switch.UseLegacyAccessibilityFeatures=false"/>
</runtime>
###Affected APIs
* Not detectable via API analysis
<!--
### Original Bug
[492954] (https://devdiv.visualstudio.com/web/wi.aspx?pcguid=011b8bdf-6d56-4f87-be0d-0092136884d9&id=492954)
Doc: Compat documentation for WCF accessibility changes in .NET 4.7.1
-->

35
Documentation/compatibility/WCFSDKToolsAccessibilityChangesIn4.7.1.md 100644
View File

@ -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
<runtime>
<AppContextSwitchOverrides value="Switch.UseLegacyAccessibilityFeatures=false"/>
</runtime>
```
- [x] Quirked
- [ ] Build-time break
### Affected APIs
* Not detectable via API analysis
### Category
Windows Communication Foundation (WCF)
<!--
### Original Bug
[492954] (https://devdiv.visualstudio.com/web/wi.aspx?pcguid=011b8bdf-6d56-4f87-be0d-0092136884d9&id=492954)
-->

21
Documentation/compatibility/wpf-accessibility-improvements.MD
View File

@ -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 ```<runtime>``` 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