Microsoft Releases .NET Framework 4.7.1

Microsoft shipped the latest iteration of its .NET Framework, version 4.7.1, adding support for .NET Standard 2.0 among a host of other improvements to accessibility, security, performance, reliability and more.

.NET Standard defines APIs that all conformant .NET implementations must provide to ensure consistent API usage across development projects, replacing the previous Portable Class Libraries (PCL) as the means to create libraries for all scenarios.

Version 2.0 of the .NET Standard made big news when it was announced in August with the addition of tens of thousands of APIs.

.NET Standard 2.0
[Click on image for larger view.] .NET Standard 2.0 (source: Microsoft).

And now, some 200 additional .NET Standard APIs are being provided with .NET Framework 4.7.1 that weren't available in v4.7 or earlier versions.

"Applications that target .NET Framework 4.6.1 through 4.7 must deploy additional .NET Standard 2.0 support files in order to consume .NET Standard 2.0 libraries," Microsoft explained in a blog post yesterday. "This situation occurred because the .NET Standard 2.0 spec was finalized after .NET Framework 4.6.1 was released. .NET Framework 4.7.1 is the first .NET Framework release after .NET Standard 2.0, enabling us to provide comprehensive .NET Standard 2.0 support."

That comprehensive support comes built-in with the new Windows 10 Fall Creators Update of Windows 10 and Visual Studio 2017 15.5, just announced in preview.

Amid a plethora of minor under-the-hood tweaks, Microsoft also: made improvements to Garbage Collection; expanded options for ASP.NET forms authentication credentials; provided customized configuration builders in addition to the current static config files; and much more.

On the GitHub site for the vast open source framework, Microsoft organized the changes by product area, so developers can dig deeper into topics that interest them, including:

One major area of focus that cuts across nearly all of the above is accessibility. Microsoft made a host of improvements designed to help developers boost the usability of their applications for all users, including those with impairments or disabilities.

Accessibility was improved for Windows Forms, WPF, WCF SDK tools and more, in the form of screen reader enhancements, high-contrast changes for controls, better narrator support and more.

The comprehensive release notes on GitHub provide more information on the myriad changes.

About the Author

David Ramel is an editor and writer for Converge360.

comments powered by Disqus


  • Visual Studio Code Dev Team Cleans Up

    The Visual Studio Code development team focused on some housekeeping in the October update, closing more than 4,000 issues on GitHub, where the cross-platform, open-source editor lives.

  • ML.NET Model Builder Update Boosts Image Classification

    Microsoft announced an update to the Model Builder component of its ML.NET machine learning framework, boosting image classification and adding "try your model" functionality for predictions with sample input.

  • How to Do Naive Bayes with Numeric Data Using C#

    Dr. James McCaffrey of Microsoft Research uses a full code sample and screenshots to demonstrate how to create a naive Bayes classification system when the predictor values are numeric, using the C# language without any special code libraries.

  • Vortex

    Open Source 'Infrastructure-as-Code' SDK Adds .NET Core Support for Working with Azure

    Pulumi, known for its "Infrastructure-as-Code" cloud development tooling, has added support for .NET Core, letting .NET-centric developers use C#, F# and VB.NET to create, deploy, and manage Azure infrastructure.

  • .NET Framework Not Forgotten: Repair Tool Updated

    Even though Microsoft's development focus has shifted to the open-source, cross-platform .NET Core initiative -- with the aging, traditional, Windows-only .NET Framework relegated primarily to fixes and maintenance such as quality and reliability improvements -- the latter is still getting some other attention, as exemplified in a repair tool update.

.NET Insight

Sign up for our newsletter.

Terms and Privacy Policy consent

I agree to this site's Privacy Policy.

Upcoming Events