.NET Framework vs .NET Core vs .NET vs .NET Standard vs C#

What is the difference between .NET Framework and .NET Core? Where does .NET fit in? Is .NET Standard another framework? What about the versions of C#? How do they relate to the .NET Framework/Core/.NET/Standard? These are the questions we are going to answer in today's episode of Dev Questions.

[droam]

I’ve probably googled this question a dozen times over the past couple years, and this is the first time I’ve understood it. Thank you, Tim.

[williamliu]

"William" has just finished this video. I still can`t believe that my question was answered here..!! Very clear answer for me. I appreciate it, Tim! ❤

[yunietpiloto]

Man why I didn’t have a university professor like you. Spot on!

[_rcs]

Tim, you were my go-to resource when I was stuck developing with WebForms and was trying to build modern skills. I'm glad you are still producing quality content. I hope it's going well for you.

[gcma]

I was so lost thinking that NET Core was different from plain .NET. Thank you so much, very detailed and patiently explained.

[ricardodelacruz]

Thanks for that great explanation! I speak English and Spanish and this is by far the best video in both languages that I’ve found on the web explaining the difference between all of the confusing concepts of .Net, I was so frustrated that I couldn’t found a video or document that explains all of that but you have done it in a easy and excellent way, thanks a

[ETO]

Shared this to the team to clarify the need for migration. Thank you, my man!

[jasonfreeman]

Wondering why you haven’t mentioned the support libraries as well. I think this is what you meant when you used the term “abstraction layer”. Any language on a given platform requires all kinds of helpers to do things like open files, communicate via the network, print, and common tools like lists, stacks, numerical processing, etc. Framework required pre-installed libraries. These libraries tended to be monolithic (large and not very modular). Core modularized and packaged parts of the framework libraries allowing developers to pick and choose the parts of the “libraries” they needed for an application. This was necessary for a couple of reasons. One, cloud servers needed to be fast to spin up. Requiring that the entire set of framework libraries be present increased storage consumption and install time. Two, the framework had a bigger footprint because it was all one big thing and it would load and initialize things that the app may never use. So modularizing it and enabling the dev to specify only what was needed made application installation smaller and faster and it also made application startup smaller and faster. Framework = monolithic install. Core = modular packaging.

[stevenbingham]

I would have loved some graphics to accompany this discussion, but even without graphics the representation was easy to follow. Nice job.
I've worked with Microsoft software/systems since the 80's and one thing I can say is you really need to understand the historical progression of its systems to really appropriately understand where thing are. This simple discussion of the progression and reasoning behind going from Framework to Core is an example of how drawing that historical background is truly helpful.

[timneale]

Thank YOU!!! Being new to Developing this really helped answer a question I didn't even really know I had. Awesome explanation, can't wait to watch more of your stuff.

[digestingpuma]

Love this video and Tim's explanation. The way he explains it, his conversation pace makes it much, much easier for me to understand the topic.

[moneyhustle]

Tim I have been confused by this for so long. This was hands down one of the best explanations I have ever seen for such a complex topic. SALUTE!!!

[td]

Wow man what an explanation! This cleared out my many questions.
You are really wonderful professor.
Thank you Professor Tim!

[orange-vlcybpd]

Relativity Theory < Quantum Theory < Valsiliev equations < abc conjecture < dotNET Framework Naming and Versioning System

[jeeshenlee]

Thanks, Tim. That's a great summary.

I wish to see more how-to video guides on migrating from ASP MVC (.NET Framework 4.8) to .NET 6 and migration from WPF (.NET Framework) to .NET 6

[onurguzel]

I was sick and tired researching to resolve this confusion. MS really messed up so bad. Nice video. Thanks.

[IamKVJ]

Just this single video cleared all of my confusion in dot net... Thanks man!

[geoffmreynolds]

I cannot stress enough what a great video this is. I have been confused with .net for the longest tome

[skajlet]

As always a clear explanation. It would be great if you could create a video about CIL, CLR, JIT. What they are, what they do and how they depend on each other. Thank you for your commitment.

[anthonyaddo]

Supremely clear explanation. And done in such a communicative, casual way. You're doing a great service!!