The Most Exciting Promise of .NET 5
Why all C# developers should be paying attention to this upgrade release in November 2020.
saint4eva
Nice article. Thank you
Efraim T.
Thanks
Nathi
Interesting read about .NET 5
Manoj
nice post
Akeem Aweda
Great Post!
sadashiv
Their naming convention of different frameworks is really confusing and very disappointing also. I am not getting why again they are moving back to their previous version naming like. Net 5.0. Already they were into latest. Net core 3.2.Why could not they continue with. Net core 4.0/5.0 like that?? Because now core means open source and more over platform independent. Such a shitty decision again by Microsoft then to again moving back to previous naming conventions just to confuse. Net developers. I hate their useless strategy 
Sid G
Using the phrase “completely different set of APIs and libraries” is hyperbolic. Many applications will see no change.
togakangaroo
It seems silly that I would have to mention it given how this article started but uhh…its not “Unity” if you don’t have “Unity” on that list. Folding Xamarin into .net core is nice, but there are still plenty of other BCL-based frameworks in use.
Latino
Really? This is confusing for you? 5.0 supersedes everything? What more do you need to know?
Naming it .Net core 4.0. THAT would be confusing.
sadashiv
You tell me, how it is not confusing? As per the blog, the next .Net 5.0 is going to supersede everything that we have now and it is defined as one framework to rule them all. Whether Microsoft it playing or what, like whenever they want they will switch to .Net Core versions, when they feel bored again coming back to .Net 5.0.?? What is this ? Already we know, before .Net Core, it was as I remember .Net 4.5/4.7 I think. After introducing .Net Core, it was portrayed like .Net core is going to futuristic in Dot net. Now, again what the hell , why again .Net 5.0 ?? Isn’t it confusing like after .Net 4.5 they were supposed to release .Net 5.0. But, after switching to opensource, supporting platforms outside of windows in .Net Core, again coming back to their previous versions naming like .Net 5.0 …???
Goomba
"One .NET SDK to rule them all…" 
… you just couldn’t resist to say that… 
Stephan Arnas
I am so exciting to move my project to .net 5 !
I am looking forward to your next articles about .net 5.
Latino
I don’t understand why you make such a fuss over the name. They told you the unified framework is going to be called .Net 5.0.
You read now that it is unified and you read it’s name. So now you know. End of confusion?
It’s not like you will have to learn this every time you boot your pc or anything??
How would you have named it? .Net Core 5? Would be at least equally confusing bc people would think it only has the models from the older Core version instead of all of them.
Matt Welke
.NET Core was confusing. You’d tell someone about it and they’d assume that because it had “core” in its name that it was a limited subset or a microframework or something. A unified, simple “.NET” sounds nice.
Jacquers
It was a bit more limited than the full framework, but it has pretty much caught up.
LamiaLove
Why would you be “exciting” to to do that?
Bored much?
LamiaLove
But Unity is not owned by Microsoft.
What would be the point of discussing about 3rd parties?
José
I no longer develop in .NET… I use Java, i’m not stupid, donkey! - .Net 20 years later it still only runs on Windows
Xileer
I still use .NET Framework for one simple reason - File size.
Create a “Hello World” app in .NET Framework, and .NET Core. Use the default in-VS things (In VS - Not archaic third-party command-line arguments) to strip down that .NET Core binary all you want - Have it non-standalone, targeting Windows, and assume the .NET Core Framework (…) is installed on the target machine. And you know what you end up with?
A binary around 20 times larger than the default .NET Framework version.
That is simply not acceptable. An out-of-the-box Hello World with the default settings (Create new Console App, Run, examine) should NOT be 168KB. This is insane.
I have a .NET Framework Console app that’s 3,000 lines of code over 18 class files with an embedded DLL to make LDAP Calls on Linux (Courtesy of https://github.com/flamenci… - Something which .NET Core cannot do, mind you, despite its cross-platform claims - https://github.com/dotnet/r… ), and it comes in at… 143kb (About 55kb without the embedded DLL)
How does an entire .NET Framework project with more functionality than .NET Core end off SMALLER than the default “Hello World!” .NET Core application?!?!?!?
Do you want to know why this is relevant?
Browse along to C:\Windows and search for *.exe - If all of those were made in .NET Core my OS wouldn’t be able to fit on my SSD. And if that’s the future of Windows, then something is very, VERY wrong!