As anyone in the .NET community who hasn't been living under a rock will know, there's a lot of exciting things happening with .NET at the moment with the announcement of the open source, cross platform, .NET Core. However, partly due to the very open nature of its evolution, there's been a whole host of names associated with its development - vNext, ASP.NET 5, ASP.NET Core, .NET generations etc.

In this post I'm going to try and clarify some of the naming and terminology surrounding the evolution of the .NET framework. I'll discuss some of the challenges the latest iteration is attempting to deal with and how the latest developments aim to address these.

This is really for those that have seen some of the big announcements but aren't sure about the intricacies of this new framework and how it relates to the existing ecosystem, which was my situation before I really started digging into it all properly!

Hopefully by the end of this article you'll have a clearer grasp of the latest in .NET! 

A quick guide on how to properly instantiate and use HttpClient in .NET

Building a project that target .NET Framework 4.5 in Visual Studio 2022 

In .NET 5, a stack overflow will print out the stack trace 

ApiBoilerPlate - A Project Template For Building ASP.NET Core APIs In .NET Core 3.x 

 There is a known issue in the .NET Framework considering the "fa-IR" culture. 

Code Contracts provide a language-agnostic way to express coding assumptions in .NET programs. 

.NET 7 💥 - Angular Authentication with JWT (JSON WEB TOKEN)

In this video we will be going to be exploring the full authentication process from frontend with Angular and backend with WebApi and database as SQLite with JWT