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.
@@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.
@@bjojosimpson 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.
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 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 can't believe it. This is the most comprehensive explanation for .NET that I've ever heard. And it comes from The Big Show? Like really. Big thanks anyway!!
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.
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
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.
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.
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.
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#.
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.
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.
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.
Thank you so much. I left .NET FW in 2007 and moved to Java. Now the time has brought me in back to .NET and i was super confused…this clears the air…Big Thanks.
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
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. 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.
.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.
I bought a book called Pro C# 10 with .NET 6, because I aim not to only be good at C#, but to deeply understand it and the framework itself. Your video is great in helping me understanding it
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.
wow, as someone who is transitioning from data engineer/ETL developer to .NET engineer...this channel is absolute gold. Subscribed, and I should have done it a long time ago.
FINALLY! Someone who can explain the difference. When I started, my coworkers told me "We are NOT using C# or .Net(blah blah). We use .Net framework using C#" It was like WTF. Thanks to you, the confusion is lifted.
Wow...you really clarified this question for me. I have been writing C# for many years and could not understand some of the most basic aspects of the tools I was using. IAM FREE!!
New to C# and the thing which is diffrent for me is that now i undrstand to many concepts which i ignored them before. Thanks a lot for explaining these things really awesome ☺️
Thanks for the brilliant explanation. I've been away from .NET, Microsoft and C# for almost 10 years and got super confused as to which framework I should be using because I thought there were two frameworks being developed concurrently.
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!
@@IAmTimCorey i apologize for my autocorrection. I meant to say that the video left me confused. I am not a developer, but I needed to write a small submodule/assembly in c#/.net code recently following a sample. While I succeeded at the task, I was not able to fully understand why my code had to target ".net framework 3.5" and what implications this constraint had. From your video, I was hoping to understand why .net core or standard was not chosen as a target instead, and possibly what I might have to to i the future to update this submodule.
Ok, I understand. So .NET 3.5 is not compatible with the other .NETs. It is an older version. Like with most software, the older versions do not support the newer versions. Newer versions support older versions usually but not the other way around.
@@IAmTimCorey Thank you for your response. I would have expected some such too, but here is where it gets even more confusing (for me). The assembly I created is a mod for a Unity 5.6 game (Cities Skylines), which is based on "Mono" which is as I understand, an open-source implementation of .Net 3.5. So, mods for this game are expected to target .Net 3.5 per the specification of the game. However, there are many mods for this game that are mistargetted (to .Net 4+) and yet they appear to function correctly in this .Net 3.5 environment. There is some compatibility feature that makes this possible, somewhere. I suspect the mistargetting happens due to the default target setting in Visual Studio, and not due to a deliberate choice by the mod's developer, and that those mods use only the most basic features of .net (eg, booleans, arrays, etc), and since the functionality of these features has not changed since 3.5, the 4.0+ implementation is compatible too. But this also means that 4.0 mods that make use of features new to 4.0 may function incorrectly in Cities Skylines. This game has very poor failure management, so non-existing features will cause indeterminate failure modes.
Just like me, after watching this video, Microsoft owes you big time, to clear all the confusion and boost .net developers' confidence. Thank you so much from the bottom of my heart 👍 God Bless you Sir!!
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!
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 !!!
Regarding the statement that upgrading versions is easy and that an “intern can do it in 20 minutes.” While that may be true, sometimes there are complexities beyond the tech. For instance, I work in a highly regulated industry. As simple as that change may be, going from one major version to another requires a complete, full, regression. That means re-running every test case, screenshots, validations, verifications, etc. This takes many person hours, and takes people away from current feature work. There are certainly things that could be done to improve that process, but then something else has to give. That said, the 3 year / 15 month cycle seems like a reasonable approach to keep things moving with .NET.
So as far as management at my company goes, we have had a .net web app for a decade. Its a treat to explain we need to spend 6-12 months to convert to .net.
I bet. It is always hard to sell what looks to be an expense without gain. While it still won't be easy, try discussing the speed improvements, improved security, and additional features you can add. Give them a reason to say yes.
Thanks - great video. I was today's years old when I discovered that .NET core/ NET5 does not support the chart tool. You have to build in .NET Framework if you want a chart on your windows form.
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.
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.
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.
@@bjojosimpson 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.
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.
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.
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!
I can't believe it. This is the most comprehensive explanation for .NET that I've ever heard. And it comes from The Big Show? Like really.
Big thanks anyway!!
You are welcome.
Shared this to the team to clarify the need for migration. Thank you, my man!
Great!
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!
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.
give this dude a medal, you explained it so well and it's so easily understandble. well done my freind.
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.
i watched many videos trying to understand this...but THIS IS WHERE MY SEARCH ENDED!!! Thank You
Excellent!
Wow man what an explanation! This cleared out my many questions.
You are really wonderful professor.
Thank you Professor Tim!
Awesome!
Just this single video cleared all of my confusion in dot net... Thanks man!
Great!
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.
Supremely clear explanation. And done in such a communicative, casual way. You're doing a great service!!
Thank you!
Relativity Theory < Quantum Theory < Valsiliev equations < abc conjecture < dotNET Framework Naming and Versioning System
Naming is hard.
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!
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.
The best clear and concise explanation ever came up with. You rock Tim
Thank you!
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#.
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.
Thank you, Tim! (Your videos on UA-cam and classes at IAmTimCorey are great!)
Thank you!
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.
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 :)
Thank you so much. I left .NET FW in 2007 and moved to Java. Now the time has brought me in back to .NET and i was super confused…this clears the air…Big Thanks.
I’m glad it was helpful.
Fantastic explanation. Thank you!
You are welcome.
I cannot stress enough what a great video this is. I have been confused with .net for the longest tome
Glad it helped!
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
Essential video for someone just getting into the .NET world like me. Thank you a lot!!
You are welcome.
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.
What an Explanation of a Complex Eco-System into an Easy to Digest hierarchy. Thank you for being on UA-cam for Us
Glad you like it!
I just love this guy, unbelievably succinct!!
Thanks!
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.
.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.
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.
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.
Very well done. Not everyone can breakdown things in a way that is easy to understand.
Thank you!
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.
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.
I bought a book called Pro C# 10 with .NET 6, because I aim not to only be good at C#, but to deeply understand it and the framework itself. Your video is great in helping me understanding it
I am glad it was helpful.
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!
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.
wow, as someone who is transitioning from data engineer/ETL developer to .NET engineer...this channel is absolute gold. Subscribed, and I should have done it a long time ago.
I am glad it is so helpful.
I think your courses are too expensive for me but I support and love your free stuff, thank you!
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.
FINALLY! Someone who can explain the difference. When I started, my coworkers told me "We are NOT using C# or .Net(blah blah). We use .Net framework using C#" It was like WTF. Thanks to you, the confusion is lifted.
I'm glad it was so helpful.
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.
Wow...you really clarified this question for me. I have been writing C# for many years and could not understand some of the most basic aspects of the tools I was using. IAM FREE!!
Awesome!
The best video I have seen so far which explained these confusing terms in such an easy way. Thanks Tim :)
Excellent!
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!
as new to C# and .NET ecosystem , this video clear things out. thank Tim.
You are welcome.
I am not up-to-date with technology change all these years. After listening to your videos, here come a new subscriber with notifications!
.net standard will support windows desktop applications too?
Great! And it depends. A desktop application can consume/use a .NET Standard library. A desktop app cannot be a .NET Standard project, though.
They said naming things is the hardest task developers do. Well said!
Thanks!
That was an awesome overview of the past 20 years!
Thanks!
This is one of those things where having a simple diagram would greatly help explain this topic.
Stay tuned. 😉
I've always been confused about .NET's names, great explanation thank you.
I’m glad it was helpful.
New to C# and the thing which is diffrent for me is that now i undrstand to many concepts which i ignored them before. Thanks a lot for explaining these things really awesome ☺️
You are welcome.
This is the best explanation to the differences between all of these. Thanks a lot!
You're very welcome!
You seriously should be name Tim Dot Core Y .. Thanks We all need this explanation big times.
Thank you!
Cool, finally I have a clear vision what net standard is used for, thanks Tim!!!
Great!
Thank you for clearing that up. I was so confused about all of these naming conventions.
Thanks for looking to Tim for the answers!
Amazing explanation! I've been googling this for days and only now I could nail it. Thanks a lot
Glad it helped!
Thanks for the brilliant explanation. I've been away from .NET, Microsoft and C# for almost 10 years and got super confused as to which framework I should be using because I thought there were two frameworks being developed concurrently.
I am glad it was helpful.
Never understood this before I watch your video..Very very informative. Thank you.
You are welcome.
Thanks Tim for this clear and easy to understand video. All your videos are just amazing. Thank you very much.
You are welcome.
Very detailed yet simple explanation. Thanks TIm
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.
I spent 25 really useful minutes watching this. Thanks Tim!
You are welcome.
Best explation heard so far....Cleared most of the doubts... Appreciate it
Excellent!
I loved the way you explained. Now I have a clear picture of .net.
I am glad it was helpful.
Finally, a clear explanation! Thank You, great video!
Thanks for trusting Tim in your coding journey.
Your explanation might makè sense to those who already understand thw differences, but it left me just just as convinced.
What are you convinced of? I’m confused.
@@IAmTimCorey i apologize for my autocorrection. I meant to say that the video left me confused. I am not a developer, but I needed to write a small submodule/assembly in c#/.net code recently following a sample. While I succeeded at the task, I was not able to fully understand why my code had to target ".net framework 3.5" and what implications this constraint had. From your video, I was hoping to understand why .net core or standard was not chosen as a target instead, and possibly what I might have to to i the future to update this submodule.
Ok, I understand. So .NET 3.5 is not compatible with the other .NETs. It is an older version. Like with most software, the older versions do not support the newer versions. Newer versions support older versions usually but not the other way around.
@@IAmTimCorey Thank you for your response. I would have expected some such too, but here is where it gets even more confusing (for me). The assembly I created is a mod for a Unity 5.6 game (Cities Skylines), which is based on "Mono" which is as I understand, an open-source implementation of .Net 3.5. So, mods for this game are expected to target .Net 3.5 per the specification of the game. However, there are many mods for this game that are mistargetted (to .Net 4+) and yet they appear to function correctly in this .Net 3.5 environment. There is some compatibility feature that makes this possible, somewhere. I suspect the mistargetting happens due to the default target setting in Visual Studio, and not due to a deliberate choice by the mod's developer, and that those mods use only the most basic features of .net (eg, booleans, arrays, etc), and since the functionality of these features has not changed since 3.5, the 4.0+ implementation is compatible too. But this also means that 4.0 mods that make use of features new to 4.0 may function incorrectly in Cities Skylines. This game has very poor failure management, so non-existing features will cause indeterminate failure modes.
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.
Loving the upgraded quality on the channel!
Thanks!
Very Well Explained Tim, I was confused about all these frameworks and their confusing names.
Thanks!
Very well explained and with no need for diagrams!
Thanks!
Just like me, after watching this video, Microsoft owes you big time, to clear all the confusion and boost .net developers' confidence. Thank you so much from the bottom of my heart 👍
God Bless you Sir!!
Thank you!
I work as a software engineer at Microsoft and I didn’t know lol. Thank you for knowing what my job is about more than I do
lol happy to help.
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!
Detailed and clear as usual. Thanks so much for the explanation!
You are welcome.
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!
Thank you!! I have been puzzling with this for a couple of days
You are welcome.
Regarding the statement that upgrading versions is easy and that an “intern can do it in 20 minutes.” While that may be true, sometimes there are complexities beyond the tech. For instance, I work in a highly regulated industry. As simple as that change may be, going from one major version to another requires a complete, full, regression. That means re-running every test case, screenshots, validations, verifications, etc. This takes many person hours, and takes people away from current feature work. There are certainly things that could be done to improve that process, but then something else has to give. That said, the 3 year / 15 month cycle seems like a reasonable approach to keep things moving with .NET.
Yep, there’s a balance. Wait too long and you end up with outdated, insecure tech. Upgrade too fast and you never get new features.
So as far as management at my company goes, we have had a .net web app for a decade. Its a treat to explain we need to spend 6-12 months to convert to .net.
I bet. It is always hard to sell what looks to be an expense without gain. While it still won't be easy, try discussing the speed improvements, improved security, and additional features you can add. Give them a reason to say yes.
Thank you Tim for the wonderful video...It was always confusing to get the difference between these three..Now it is more clear..
Great!
Thanks - great video. I was today's years old when I discovered that .NET core/ NET5 does not support the chart tool. You have to build in .NET Framework if you want a chart on your windows form.
You are welcome.
Thanks. Very well explained. I have .net experience and was very confused. Now I do understand.
Great!
Perfect explanation video of .net history, it enlightened me a lot. Thanks a lot, Tim.
You are welcome!
Great explanation, i have this question from months. Clarified thanks
I am glad it was helpful.
Thank you Tim. You're such a great teacher.
You are welcome.
@@IAmTimCorey ☺️☺️
Thankyou TIM for great explanation !! Best wishes from Nepal! ❤️
You are welcome.
This video helped me to understand documents a lot better.
Great!
This was such a necessary video. Thanks for demystifying .NET.
You are so welcome!