.NET Framework vs .NET Core vs .NET vs .NET Standard vs C#
Vložit
- čas přidán 11. 05. 2024
- 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.
Podcast: iamtimcorey.com/p/podcast
Purchase Courses: iamtimcorey.com
Mailing List: signup.iamtimcorey.com/
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.
I’m glad it was helpful.
@@IAmTimCorey You have the gift of explaining and teaching. Truly appreciate your time articulating so much knowledge. Wishing you the best, Tim.
@@IAmTimCorey Thanks for explaning! Finally understand the different after coding in C# for 7 years.
@@IAmTimCorey god is bold
why not bingit ;d
"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! ❤
Awesome!
Thank you. A friend has tried to explain this several times, but I still get confused. This really helps. I never thought to ask in here! Thank you again.
Man why I didn’t have a university professor like you. Spot on!
If they are at the university, than they are rarely in the real business world actually doing it.
@@tomthelestaff-iamtimcorey7597 Honestly this might be an over simplification, a number of my co-workers when I worked at Microsoft also taught classes at the University of Washington.
@@dand4485 True, there are some exceptions. I did encounter one in my years a the university.
In my opinion university professors spend so much time mastering subjects to the point where they lose touch with what is it like to be a beginner.
@@none_the_less That might be true but, but then again wouldn't expect universities the place for beginners, especially if the topic is on advanced topics, where the level of professors covering the hard stuff, more often they won't be teaching introductory classes? While some of the best teachers I had where the upper professors teaching the simple stuff. Found more often they cut out the chatter and presented stuff clearly in a way only a person with great understand might. Having as much mastery of a subject they really would make it that much simpler and earlier for other to understand. Hard having a person that doesn't really understand a subject themselves teach it too...
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.
I am glad my content has been so helpful.
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 lot!!!!!!!
I am glad it was so helpful.
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.
Thank you.
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.
You are most welcome. Thanks for watching.
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!!!
I am glad it was so helpful!
Shared this to the team to clarify the need for migration. Thank you, my man!
Great!
Thank you, Tim! (Your videos on CZcams and classes at IAmTimCorey are great!)
Thank you!
Wow man what an explanation! This cleared out my many questions.
You are really wonderful professor.
Thank you Professor Tim!
Awesome!
Thank you so much for such a simple yet detailed explanation! This was so confusing before and now it is crystal clear.
Glad it was helpful!
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
I added it to Tim's list for topics to consider. Thanks for recommending it.
@@tomthelestaff-iamtimcorey7597 Hey, just wanted to ask if it was possible to make a video about it? Thanks for the content you provide.
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.
I am glad you enjoyed it.
The best clear and concise explanation ever came up with. You rock Tim
Thank you!
I've been scratching my head over this confusion for quite some time and this video finally put an end to that confusion. Thank you so much for this great explanation.
Glad it helped!
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.
The CLR is the runtime kind of like the JVM; just think of it as a Virtual Machine. Think of CIL as some kind of Assembly Code that the Virtual Machine understands. The JIT converts CIL to the instructions of the underlying hardware as the program runs. For instance, a program written in C# can be compiled to CIL just once (depending on your compiler switches) and then run on different architectures - x86, x64, ARM, ARM64. It is the responsibility of the JIT on the given platform to convert the CIL to actual machine code for that platform as the program runs.
I a great explanation in other comments, but I still placed it on Tim's viewer suggestions list.
Just this single video cleared all of my confusion in dot net... Thanks man!
Great!
Wow !!!
This is spot on fantastic explanation.
Now I have clear picture about my learning path ahead.
Thanks a lot, Tim.
And as always you are Tim Corey !!!
I’m glad it was helpful.
Thanks for this Tim. Great content. I updated my setting for your channel to notify on all videos.
Awesome!
Fantastic explanation. Thank you!
You are welcome.
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.
Thank you.
thank you
Thank you 👍🏼.
Thanks but what about ".NET Standard"?
It's not only about libraries, its also about how the language is written fundamentally ( indentation, use of brackets, Dense Matrix Multiplication)...so on. These are very important to be written and organised on the hardware memory using very low level languages (Assembly) or maybe C/C++. Most languages have their own unique way to write and organise that specific memory and having a Framework that unites all of these "Abstractions" is huge.
So, instead of having to use 5 languages to write an application on different platforms, now you can use only 1. Which in our case C#.
The best video I have seen so far which explained these confusing terms in such an easy way. Thanks Tim :)
Excellent!
Thanks man. I don't think anybody would care to break it down more concisely than how you did in this video. 25 mins. Well put out.
Thank you!
I just love this guy, unbelievably succinct!!
Thanks!
Tim, it will have been nice to use the display devices behind you to give us illustrations that will go with your explanation!
I had to do my own illustrations while you explained.
I don’t have a display behind me. That’s my bookshelf.
@@IAmTimCorey :)
Thanks for the clarification! Really appreciate the time and effort you spent in making this video
You are welcome.
Thank you for a brilliant explanation!
And yeah, these things confused me while studying SC and only now I have seamless understanding of what's going on there. Great video!
Excellent!
Relativity Theory < Quantum Theory < Valsiliev equations < abc conjecture < dotNET Framework Naming and Versioning System
Naming is hard.
Hello Tim, excellent explanation, thanks clears several confusion points for me.
I do have a question - what do they mean say ".NET Core X has support for 3 years" does it mean they will fix any bugs identified in that version or they will only be backward compatible for 3 years back
They will fix bugs in that version.
Usually a life time for something is the developer basically saying, after three year's we're not working on this except for major security patches, after five years we're done, it's dead, use at your own risk.
The main thing to keep in mind is if three years from now a third party library is going to be updating to a new version, that's pretty much the number one thing that kills code when a version expires, the libraries ti depends on moving on to the latest version.
Thank you for clearing that up. I was so confused about all of these naming conventions.
Thanks for looking to Tim for the answers!
What an Explanation of a Complex Eco-System into an Easy to Digest hierarchy. Thank you for being on CZcams for Us
Glad you like it!
Hey Tim, thank you for the explanation! What about ASP.NET and ASP.NET Core? Where and when did they come from?
Same thing. ASP.NET is the web project types in the .NET Framework. ASP.NET Core is the web project types in .NET Core.
@@IAmTimCorey So they use different abstraction layers or same? I mean does asp.net use .net framework and asp.net core uses .net core?
@@irfanshaik1302 Right Question
.Net Core - Naming confusion not helped by many libraries for. Net Framework having base components in libraries named along the lines of MyLibrary.Core. Also MS screwed up big time with their Identity libraries. TBH, I still can't shake the incompatibility impression of the original .Net Core release. All this isn't helped by the muddled online documentation.
Yup, clear as mud.
It's what happens when the marketing people get involved in technical matters.
Detailed and clear as usual. Thanks so much for the explanation!
You are welcome.
Amazing explanation! I've been googling this for days and only now I could nail it. Thanks a lot
Glad it helped!
Why did Microsoft make this so damn confusing in the first place? They're terrible at communicating
I think I explained that in the video.
To start with the obvious: .NET is a terrible name
Yep.
even the languages name of C# or F# . They need to get their naming sorted out so it is easy to google without special characters.
This is the best explanation to the differences between all of these. Thanks a lot!
You're very welcome!
I cannot stress enough what a great video this is. I have been confused with .net for the longest tome
Glad it helped!
Thank you for this brilliant Explanation, It has cleared my doubt.
Thanks Tim, It was really a great way of explanation and makes me very very clear to remove the confusion on these terminologies.
You are welcome.
Thank you Tim for the wonderful video...It was always confusing to get the difference between these three..Now it is more clear..
Great!
Finally, a clear explanation! Thank You, great video!
Thanks for trusting Tim in your coding journey.
this is probably the clearest explanation I have come across, and it was pretty damn useful, with all the naming convention etc.. Thanks
You are welcome.
thanks Tim for a wonderful explanation. I am sure it couldn't be done any better.
You are welcome.
Best explation heard so far....Cleared most of the doubts... Appreciate it
Excellent!
Great summary Tim ! 👍 One could have used a slide for the multiple layers and all but this worked also fine 👏
I’m glad it was helpful.
I searched for so long for a clear explanation of the differences between .NET versions that it became frustrating. Thank you for making this video and clearly explaining everything.
I am glad it was so helpful.
Cool, finally I have a clear vision what net standard is used for, thanks Tim!!!
Great!
give this dude a medal, you explained it so well and it's so easily understandble. well done my freind.
Thank you!
Thanks Tim for this clear and easy to understand video. All your videos are just amazing. Thank you very much.
You are welcome.
Thank you for great explanation I am a starting with c# and finally I can understand the difference between the different .net
Excellent! I am glad it helped.
That was an awesome overview of the past 20 years!
Thanks!
Thank you!! I have been puzzling with this for a couple of days
You are welcome.
Tim, once again, a job well done!
Thanks!
You are welcome.
Very well done. Not everyone can breakdown things in a way that is easy to understand.
Thank you!
This was so clear!
Great job Tim!
Thanks
You're very welcome!
This was such a great video, thank you so much for the content!
You are welcome.
Thanks so much for this video - really helped me get back up to speed with things!
You are welcome.
Thank you for the history and easy explanation. Nothing is difficult, it's just how you are taught that makes it hard or difficult. You made it easy.
You are welcome.
Brilliant, crystal clear explanation, thank you. 👏
You are welcome.
Essential video for someone just getting into the .NET world like me. Thank you a lot!!
You are welcome.
Thank you Tim. You're such a great teacher.
You are welcome.
@@IAmTimCorey ☺️☺️
Answered a LOT of questions and cleared things up. Thanks
Excellent!
Very detailed yet simple explanation. Thanks TIm
You are welcome.
Very Well Explained Tim, I was confused about all these frameworks and their confusing names.
Thanks!
Your explanation was very easy to understand. thank you!
とてもわかりやすかったです。ありがとう！
You are welcome.
Great explanation Tim. Thanks for clarifying!
You are welcome.
Well explained. Thank you TimCorey.
You are welcome.
I was sick and tired researching to resolve this confusion. MS really messed up so bad. Nice video. Thanks.
I am glad it was so helpful.
Great explanation, i have this question from months. Clarified thanks
I am glad it was helpful.
Loving the upgraded quality on the channel!
Thanks!
Thank you professor Tim. The topic is really useful for me.
We are glad you found it helpful
Perfect explanation video of .net history, it enlightened me a lot. Thanks a lot, Tim.
You are welcome!
Exactly the video I needed! Thanks for this :)
You are welcome.
Great explanation, sir. I just found your channel thanks to this video. In fact, I just installed .net core on my Ubuntu dev box just to see how it works. Thanks, man!
You are welcome.
Thanks Tim. Cleared the air quite a bit.
Glad it helped.
Thank you for the detailed and very clear explanation!
You are welcome.
thank you. After listening to the explanation, I was able to understand the changes in various .NET versions. And, it solved the confusion that comes from ignorance.
Awesome! I am glad it was helpful.
Wow. I’m speechless. This and you were perfect, thx!!
You are welcome.
as new to C# and .NET ecosystem , this video clear things out. thank Tim.
You are welcome.
Thank you!!! It all makes sense now
You are welcome.
Thanks for this. It was very disappointing to get confused with all these things after working for many years in net framework. This helped a lot..
Thanks for watching and being part of Tim's community.
Thanks for the clarity. I spent over an hour in MS docs and didn't get this level of understanding.
I’m glad it was so helpful.
Thanks for the concise explanation. As a Java developer who hasn't kept up with .NET, I learned more from your video than I have Googling the topic in my spare time.
You are most welcome. Thanks for watching.
Never understood this before I watch your video..Very very informative. Thank you.
You are welcome.
You have provided me an extraordinary answer to my boss why I need to start over and rewrite all my .net frameworks applications in my previous 10+ years.
Great!
Nice. Your videos are always useful.
Great!
Great explanation! exactly what i was looking for
Glad it was helpful!
I was so lost thinking that NET Core was different from plain .NET. Thank you so much, very detailed and patiently explained.
You are welcome.
Thank you very much Mr Tim for the great explanation
You are welcome.
Thankyou TIM for great explanation !! Best wishes from Nepal! ❤️
You are welcome.
I've always been confused about .NET's names, great explanation thank you.
I’m glad it was helpful.
Thank you for the Awesome explanations.
You are welcome.
Thank you SO MUCH for this!
You are welcome.
Excellent this helps a lot, PPT will help us to refer it again
Glad it was helpful!
That was a great explaination. Thanks dude.
You are welcome.
Your content has been such a great help over the years!
Thank you!
I spent 25 really useful minutes watching this. Thanks Tim!
You are welcome.