daohualiuxiang
/
dotnet
mirror of https://github.com/microsoft/dotnet.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
dotnet/releases/net471/dotnet471-known-issues.md

18 lines
3.6 KiB
Markdown
Raw Normal View History

Initial changes for adding known issues (#450) Initial changes for adding known issues
2017-08-01 08:38:34 +08:00
.NET Framework 4.7.1 Known Issues
=================================
Merge latest from net471 into master * Regenerated readme, made changes to build readme (#520) * Replaced asset IDs with xrefs (#521) * Replaced asset IDs with xrefs * Formatting changes * .NET 4.7.1 Publishing Changes (#510) * Updates for Known Issues * Updates for Known Issues * Updates for Known Issues * Added API diffss for 4.7.1 * Added updates to 4.7.1 change list * Updates for readme, changelist and known issues * Fixed as per comments from rpetrusha
2017-10-18 05:13:24 +08:00
This document lists the known issues that you may experience after you install the Microsoft .NET Framework 4.7.1.
Initial changes for adding known issues (#450) Initial changes for adding known issues
2017-08-01 08:38:34 +08:00
Merge latest from net471 into master * Regenerated readme, made changes to build readme (#520) * Replaced asset IDs with xrefs (#521) * Replaced asset IDs with xrefs * Formatting changes * .NET 4.7.1 Publishing Changes (#510) * Updates for Known Issues * Updates for Known Issues * Updates for Known Issues * Added API diffss for 4.7.1 * Added updates to 4.7.1 change list * Updates for readme, changelist and known issues * Fixed as per comments from rpetrusha
2017-10-18 05:13:24 +08:00
## Product issues for the .NET Framework 4.7.1
Add known issue for 470006 - GC large object crashes Added a known issue, written by Chris Ahna, about GC crashes when we have a high rate of large object allocations and frees.
2018-02-07 01:28:12 +08:00
- [470006 - GC - Rare crashes can occur when background GC is enabled in applications which allocate and free large objects at a high rate](https://github.com/Microsoft/dotnet/blob/master/releases/net471/KnownIssues/470006-GC%20Crashes%20with%20high%20rate%20of%20large%20object%20allocation.md)
Update known issues for #521954
2017-11-09 09:20:10 +08:00
- [479874 - WPF - Touch Stops Working After Rapid/Prolonged Use Of Popups](https://github.com/Microsoft/dotnet/blob/master/releases/net471/KnownIssues/479874-WPF%20Touch%20Stops%20Working%20After%20Prolonged%20Use%20of%20Popups.md)
- [481090 - WPF - Touch generates a NullReferenceException in WispLogic.ProcessInputReport](https://github.com/Microsoft/dotnet/blob/master/releases/net471/KnownIssues/481090-WPF%20Touch%20generates%20NullReferenceException%20in%20ProcessInputReport.md)
- [489937 - WPF - Touch/Stylus Generates AccessViolations and Heap Corruption in GetPenEventMultiple](https://github.com/Microsoft/dotnet/blob/master/releases/net471/KnownIssues/489937-WPF%20Touch%20and%20Stylus%20AccessViolation%20in%20GetPenEventMultiple.md)
- [493108 - WPF - InvalidCastException when displaying a checked MenuItem](https://github.com/Microsoft/dotnet/blob/master/releases/net471/KnownIssues/493108-WPF%20InvalidCastException%20when%20displaying%20a%20checked%20MenuItem.md)
- [510901 - BCL - Applications targeting .NET 4.6.1 that use .NET Standard libraries might be broken when running on .NET 4.7.1](https://github.com/Microsoft/dotnet/blob/master/releases/net471/KnownIssues/510901-BCL%20Apps%20targeting%20.NET-4.6.1%20that%20use%20.NET%20Standard%20libraries%20might%20be%20broken%20when%20running%20on%20.NET%204.7.1.md)
- [521954 - BCL - CultureAwareComparer with ignore casing serialized on previous versions of .NET Framework does not correctly deserialize on .NET Framework 4.7.1](https://github.com/Microsoft/dotnet/blob/master/releases/net471/KnownIssues/521954%20-%20BCL%20CultureAwareComparer%20with%20ignore%20casing%20on%20serialized%20on%20previous%20versions%20of%20.NET%20do%20not%20correctly%20deserialize%20on%20.NET%204.7.1.md)
Update dotnet471-known-issues.md
2017-11-22 11:08:08 +08:00
- [517815 - BCL - Applications making heavy use of System.Diagnostics.StackTrace or Exception.StackTrace might run more slowly on the .NET Framework 4.7.1](https://github.com/Microsoft/dotnet/blob/master/releases/net471/KnownIssues/517815-BCL%20Applications%20making%20heavy%20use%20of%20System.Diagnostics.StackTrace%20might%20run%20more%20slowly%20on%20.NET%204.7.1.md)
Added new known issue for 517815-BCL
2018-02-03 09:43:01 +08:00
- [517815 - BCL - Stack traces are missing source information for frames with debug information in the Portable PDB format when running on .NET Framework 4.7.1](https://github.com/Microsoft/dotnet/blob/master/releases/net471/KnownIssues/517815-BCL%20Stack%20traces%20are%20missing%20source%20information%20for%20frames%20with%20debug%20information%20in%20the%20Portable%20PDB%20format.md)
Update dotnet471-known-issues.md
2017-11-22 11:08:08 +08:00
- [523633 - Setup - Application crashes occur when running on the .NET Framework 4.7.1 after upgrading from Windows 10 Anniversary Update to Windows 10 Creators Update](https://github.com/Microsoft/dotnet/blob/master/releases/net471/KnownIssues/523633%20-%20Setup%20-%20OS%20upgrade%20to%20Windows%2010%20gets%20the%20product%20in%20bad%20state.md)
Add .NET 4.7.1 Networking known issue 534719 (#580) * Add .NET 4.7.1 Networking known issue 534719 Add known issue document for bug 534719-Networking ServicePoint.ConnectionLimit default behavior with loopback changed unexpectedly. * Addressed PR feedback
2017-12-09 08:21:42 +08:00
- [534719 - Networking - ServicePoint.ConnectionLimit default behavior with loopback changed unexpectedly](https://github.com/Microsoft/dotnet/blob/master/releases/net471/KnownIssues/534719-Networking%20ServicePoint.ConnectionLimit%20default%20behavior%20with%20loopback%20changed%20unexpectedly.md)