What are the recent enhancements to the .NET Framework since 4.5?

curiouswebster
curiouswebster used Ask the Experts™
on
What are the recent enhancements to the .NET Framework since 4.5?

What is the current latest released version? Are there any reasons to NOT use this latest version on a new .NET Framework MVC project?

So, what are the big updates since 4.5? And when was 4.5 released?

Thanks
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Commented:
Most of this information you can get from the .NET blog:
https://devblogs.microsoft.com/dotnet/

Or if you'd rather just dive into the technical details, check the GitHub repo for the releases, and you can click on each release and read the "What's new" section:
https://github.com/Microsoft/dotnet/blob/master/releases/README.md

As of this writing, the latest official version is 4.7.2. Version 4.5 isn't supported anymore. The oldest supported version is currently 4.5.2.

There are a lot of big updates, but "big" or "important" is relative to what kind of project you're working on. For example, most of my desktop apps are integrating with web services that require TLS 1.2, so an important development in 4.5 was the introduction of TLS 1.2 support in the service point manager.

As far as reasons not to use the latest version - absolutely. Let's say you write an application for your company and that application relies on some features that are specific to 4.7.2. You deploy the application to all the workstations and then realize that all the workstations are on 4.6, so they can't run your application.

So either you have to try to get the sysadmin group to upgrade to the bleeding edge (which some sysadmins will refuse to do on principle - they will intentionally stay a version or two behind the latest to avoid bugs, or maybe you'll have more confident or adventurous sysadmins - who knows), or you have to go back and rewrite code to not use 4.7.2-specific features.

It's USUALLY good practice to target the lowest-supported framework when building an application. Since .NET is backwards compatible on its 4.x versions, building an app against 4.5.2 will allow anyone with 4.5.2 or later to run the application.

Of course, that's for desktop apps - if you're on a server app, you might not have those restrictions and you can go with whatever the latest version is on the server.

Oh, also, Wikipedia's a good source for some of the "summary" information like dates when each version was released, if you want it all in one table, or some of the highlights. Just be aware that it's not AS good of a source of information as the release notes themselves, so it's good to read the blog or the release notes to get a better, more complete view of that info.
curiouswebsterSoftware Engineer

Author

Commented:
I read that the SameSite update to 4.7.2 helps reduce the risk of XSS on ASP.NET applications by removing the cookie from the response that gets passed around by the browser. Is this feature so compelling it may make some legacy user want an update to 4.7.2?

Or is there a way to code that behavior in the code for older versions of .NET?

Commented:
Well, on an ASP.NET site, you're only dealing with the server's framework. Your end users don't even need .NET - they're just hitting it via a browser.
curiouswebsterSoftware Engineer

Author

Commented:
thanks

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial