Announcing .NET Framework 4.8.1

pull/1352/head
Tara Overfield 2022-08-09 10:03:11 -07:00 committed by GitHub
parent f3cf2da6a3
commit 509d3721d8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 59 additions and 0 deletions

View File

@ -0,0 +1,11 @@
# 4.x WCF optional components
## Symptoms
The .NET Framework 4.x WCF optional components on Windows 11 ARM64 client machines will fail to be enabled either through the dism command or add/remove program UI.
## Workaround
No workaround available
## Resolution
A resolution to this issue will be included in an upcoming release
**Note**: Message Queuing (MSMQ) Activation will remain disabled because MSMQ is not available on Windows 11 for ARM64 client machines

View File

@ -0,0 +1,16 @@
# .NET Framework 4.8.1 Release Notes
You can learn about the changes made in the .NET Framework 4.8.1.
- [Download](http://go.microsoft.com/fwlink/?LinkId=2203304)
- [.NET Framework 4.8 RTM Announcement blog post](https://devblogs.microsoft.com/dotnet/announcing-dotnet-framework-481)
- [Release Notes](dotnet481-changes.md)
- [Application compatibility](https://github.com/Microsoft/dotnet/blob/master/Documentation/compatibility/README.md#net-framework-481)
- [Known issues](dotnet481-known-issues.md)
## Release Notes by Product Area
- [Native support for Arm64](dotnet48-changes.md#native-support-for-Arm64)
- [Accessible Tooltips](dotnet48-changes.md#windows-forms)
- [Windows Forms Accessibility Improvements](dotnet48-changes.md#windows-forms)

View File

@ -0,0 +1,25 @@
# .NET Framework 4.8.1 Release Notes
.NET Framework release notes describe product improvements grouped by product area.
## Native support for Arm64
* Add native Arm64 support to the .NET Framework family to leverage the benefits of running workloads natively on Arm64 for better performance when compared to running x64 code emulated on Arm64.
## Accessible Tooltips
* tooltips now comply with the guidelines set forth in the [WCAG2.1 content on Hover or Focus](https://www.w3.org/WAI/WCAG21/Understanding/content-on-hover-or-focus.html) guidance. The requirements for tooltips require the following:
- Tooltips must display either via mouse hover or by keyboard navigation to the control.
- Tooltips should be **dismissable**. That is, a simple keyboard command like the ESC key should dismiss the tooltip.
- Tooltips should be **hoverable**. Users should be able to place their mouse cursor over the tooltip. This enables scenarios like using magnifier to be able to read the tooltip for low-vision users.
- Tooltips should be **persistent**. Tooltips should not automatically disappear after a certain time has elapsed. Rather, the tooltips should be dismissed by the user moving their mouse to another control, or by dismissing the tooltip as described above.
## Windows Forms
* Added support for the UIA Text Pattern to enable assistive technology to traverse the content of a TextBox or similar text-based control letter by letter.
* Fixed high contrast issues in several controls and have changed the contrast ratio of selection rectangles to be darker and more visible.
* Fixed several DataGridView issues:
- Updated the scrollbar names for consistency.
- Fixed an issue where Narrator was unable to focus on empty DataGridView cells.
- Enabled developers to set the localized control type property for Custom DataGridView cells.
- Updated the link color for DataGridViewLink cells to have better contrast with the background.

View File

@ -0,0 +1,7 @@
.NET Framework 4.8.1 Known Issues
=================================
This document lists the known issues that you may experience after you install the Microsoft .NET Framework 4.8.1
## Product issues for the .NET Framework 4.8.1
- [ASP.NET - 4.x WCF optional components](https://github.com/Microsoft/dotnet/blob/master/releases/net48/KnownIssues/4.x-WCF-optional-components.md)