It’s time to get jazzed about the future of the .NET ecosystem!
It’s hard to believe that .NET only came out in 2002. There are so many versions of the framework, rapidly changing the places a C# developer could create and support. The entire ecosystem just turned 18, and it has been confusing at times with versioning. I fell in love with how powerful the platform was, but often, choosing to upgrade to the latest major or minor version proved difficult. How much actual value would I get from upgrading?
Can you see how naming things can be rather difficult?
Understanding what someone is talking about when they say, “.NET” is a matter of context. Since the initial release of .NET Core in 2016, There has been a clarification required whenever I was speaking about building an application. Many of the projects I worked on had a reliable experience with .NET Framework 4.5+, and reasons to upend everything and switch over to a completely different set of APIs and libraries was a daunting task. To add to the value of change question, the new versions of Framework were still being released alongside new versions of .NET Core.
The Compelling Reason to Move from .NET Framework to .NET Core
Then, C# 8 came out. We got nullable reference types and a lot more - like default implementations! Along with a new version of the language we love, came a caveat: C# 8.0 is only officially supported on frameworks implementing .NET Standard 2.1 (which the .NET Framework will never do). So while it might work, there might also be problems and only some of the language features were available. The C# 8.0 support came with the release of .NET Core 3.0.
Moving to the .NET Core environment suddenly required deeper consideration to take advantage of the benefits of C# 8. In the meantime, new versions of .NET Framework were still being shipped. In fact, .NET 4.8 was released in 2019. Having a conversation with a client about why they should spend the money to move away from the runtime that was still actively having versions released was a bit challenging, to say the least.
Wouldn’t it be nice to have one .NET to rule them all? Luckily, Microsoft agrees.
There is No More .NET Core, it’s .NET 5
Here’s the umbrella of .NET 5 to the rescue. It’s a MAJOR change because of the following reasons:
As the first part of this unification scheme, Microsoft’s Xamarin mobile development platform will switch from using the Mono BCL to join other components leveraging the .NET Core BCL. With that move, Xamarin mobile development will be folded into .NET 5. That means that for the first time, one BCL-based framework will handle all app models:
- ASP.NET Core
- Entity Framework Core
Wait, WPF and WinForms made it into .NET 5? Yes, it’s true. Hello there, old friends! Nice to see them included in this runtime. The idea of using one SDK to build apps with is pretty exciting stuff, if you ask me.
One .NET 5 SDK to Rule Them All
Who’s ready for the general availability of .NET 5 in November 2020? I know I am! Getting started working with the preview version is what we here at Okta are actively playing with, and encourage all C# developers to do the same. According to the roadmap, .NET Core has been rebranded as .NET 5 going forward, with one major version number incremented every year. Because .NET Framework was already on version 4.x, jumping to 5 would unify naming of the ecosystem going forward.
Is this end of life for the existing .NET Framework? According to Scott Hunter, the traditional platform will still be supported - at least for a while. The official support policy for .NET is stated on Microsoft’s website along with existing .NET Core versions if you are curious about a specific version sunsetting.
Current .NET Framework version 4.8 won’t evolve but some security patches will be provided for the foreseeable future.
Prepare existing apps for the future of .NET
Until general release, the best way to get prepared for .NET 5 and later is to migrate your Framework apps to the currently stable .NET Core 3.1 - particularly if you want solid GA support for C# 8 and Blazor. Breaking changes are possible with any major release, but the majority of the APIs should remain in place from .NET Core 3.x. Move your class libraries to .NET Standard 2.1 if possible to help future-proof your transition. When it comes to Xamarin, the compiler will move from the Mono BCL (base class library) to .NET Core BCL. More on mobile app migrations in a future blog post.
The .NET 5 ecosystem is still based on all previous versions of .NET Core - it’s the next logical iteration, with a dash of WinForms/WPF inclusion, faster algorithms and a bit of a rebranding. I can get behind that!
What do you think of the future of this platform? Leave a comment below and share what platform and version you are currently working with.
Long live .NET!
Learn More About .NET and .NET Core
If you are interested in learning more about how Okta can work with C# and enhance your app security, check out some of these other helpful articles:
- Build an Authenticated Web App in C# with Blazor + ASP.NET Core 3.0
- How I Learned to Love Default Implementations in C# 8.0
- Baking in Security with .NET CLI Templates
- Build Secure Microservices with AWS Lambda and ASP.NET Core
- Build a CRUD App with ASP.NET MVC and Entity Framework