.NET Core might be all the rage these days, but the original .NET Framework is still being updated. Last week Microsoft upped the version number to 4.6.2 and while it doesn’t include any killer features, it’s a solid update nonetheless.
For those who enjoy verbosity, a detailed change log is available on GitHub. Otherwise, the major areas of improvement included:
- Base Class Library
- Common Language Runtime
- Windows Presentation Foundation
- Windows Communication Foundation
I know, I know, BCL and CLR changes could mean just about anything, so let’s dive in deeper for these.
The biggest fix is support for long file names and paths. Previously, this was limited to 260 characters.
The rest of the BCL changes are security-related and can be read in full on MSDN.
As for the CLR, the only significant tweak is that null reference exceptions will now provide more extensive debugging data, if the developer so wishes. As Microsoft’s Stacey Haffner explains:
In this release, we extended the CLR debugging APIs to enable the debugger to request more information and perform additional analysis when a NullReferenceException occurs. Using this information, a debugger will be able to determine which reference is null and provide this information to you, making your job easier.
The CLR did receive a bunch of bug and performance fixes, which are described at length in the release notes.