I'm a .NET developer and have been wondering what .NET Core really is and what's different or the same as what I am used to. This was a great overview. Thanks!
0:00 - Intro 1:13 - Creating Framework and Core web MVC applications 4:20 - Comparing the two templates: structure 7:34 - Application settings 10:18 - Code behind controllers 14:55 - About .NET Core 17:27 - When to use one or the other? 19:28 - SDK dependency 20:26 - Clarification on Core for windows applications 21:26 - General advice and recommendations
Your cadence and voice are great. And an instructor that doesn't flick the mouse all over the screen when explaining things throwing the viewers eyes into chaos is other worldly. Very precise and thought out training. Nice one. Obviously the content is great too.
Glad I found this video! I'm a long time .NET developer who has been avoiding .NET Core for a long time. But you showed me all sorts of things in .NET Core that I wish I'd been able to use! I'm firing up a new .NET Core project right now! Thank you!!
I am used to working with ASP.NET MVC in the .NET Framework, but want to try working with .NET CORE for a new job prospect - this was just the kind of introduction I needed to get started...thank you!
Extremely well made video. Brushing up on .Net core for a job interview as I've never used it professionally. This is exactly what I needed! Subscribed :-)
Visual Studio code is something of a Swiss army knife IDE. It has extensions for many languages and target environments. I had some powershell script testing to do and it could all be done in the powershell ISE, but VS code was a pretty nice interface for that as well. While working on that I noticed a series of "learn Python" videos that MS was promoting and again VS Code had Python extensions to allow development in it and adds the benefit of Intellicode assistance. It's an impressive product for free.
Great video Tim, finally got around to watching this as I've not really been interested in Core before as I deal with winforms at work, however I got a project coming up for some web development and last time I did that was 10 years ago so thought I would take a look at this vid. The MVC solution looks much cleaner and easier to follow. Thanks :)
I am a fourth year college student, and this topic is given to me to report on class, I dont have an idea yet on both but you just saved my life. Thank You♥️♥️
thank you, I guess this video left me with more questions. which may be more direct ones, i went from what are the differences to why is it easier? and till what point that is subjective!... thank you very much!!!
an excellent overview that quickly identifies the high-level differences between .net core and framework. I'm new to both, so now when I sit down at my machine I can quickly identify which one my project is using. thanks for sharing!
Wow.. Great enlightenment. I have been developing MVC apps for my firm and I was wondering what .NET Core is really like. Glad I spent my good 25 minutes learning about the differences. You are great.
OK, back for round two. In round one, I made a really bone-headed comment because I mistook what Tim was doing for "Trying to do web development the long way with C# instead of taking time to learn the native languages of the browser, HTML, CSS and Javascript". Turns out, he was doing some kind of ClientServer/Desktop for native Windows code that I had no experience with, and which it turned out the the real thing he was doing was "Windows development with languages that are similar to web languages (HTML)". It was actually pretty cool, and I was totally wrong about what I was looking at. SORRY TIM. So, THIS time, I am eager to hear about .NET Core, because as an ASP.NET web developer, it looks like Core is the future.
Well explained the difference between .Net Framework and .Net Core. This video tutorial gave me a good start into understanding .Net Core. Thanks Tim for creating such a valuable piece of work.
Even after I completed your full course Tim, I have been using DotNet Core for about 10 months to a year. Yes there are some huge differences between the FullFramework and Core, but I find that I can have a full startup, database connection with a small running app in less than 30 minutes. Most of the time I just use Core for my API's then use something like Vue or Angular for my frontend. Works fairly well. One of the toughest challenges that I just figured out is setting up Roles and how to apply them to my users. Yes you can enable Authentication from the command line when you are create a project, but how do you do it after your project is built. That was a huge hurdle for me.
Adding authentication to an existing project is actually quite simple in .NET Core. You can right-click and add it to your project. I cover that in my Getting Started with .NET Core course. As for roles, we will be adding them in an upcoming video in the TimCo Retail Manager series so you can see them implemented there.
Nice video, I think .Net Core is really good, especially with Blazor, the experimental project which Microsoft is working at. Blazor will change the way web development is made now, maybe you will make a video about it? I really like it because I do not know Javascript and I should not be able to know it to do web development.
Blazor is an interesting project and I hope that it will do well. It is still quite early to do a video on it but I'm keeping an eye on it. I'll definitely do one as it gets closer to production-ready.
You shouldn’t know it to do web development (i.e, apps that run in a WEB BROWSER)??. Lol. That’s an odd comment. Maybe Blazor will shield you from learning JS but if you know C# you should be able to write JS code wo a problem. Might as well learn it instead of learning Blazor’s idiosyncrasies. But either way, someday you’ll probably need to learn it, just like devs who used web forms were shielded from anything Web-ey (html,css,js). Then they had to learn it when MVC arrived. Round and round we go.
Hi Tim ! Great presentation Very helpful for someone who just jump in Ms code world. Seems to me very confusing at first sight to chose which MS app to use. I took good note that .NET Core should be the framework to use from now one for www apps. That's correct ? Regards, Bogdan
Now that they have passed by version 4, .NET Core is now called just .NET. The current version is .NET 7. For all new applications, you want to use the latest version of .NET. I would not recommend creating anything new in the .NET Framework unless you are trying to interface it with an existing .NET Framework application.
I am .Net developer and I was kind of worried that I might have to start from scratch but I see it's the same old favourite .net with awsome improvements. Thanks for the great video
Another Big Difference is the project size . So i've created my graduation project in .net framework and got it almost done . Then we thought about moving it to .net core it was easy 90% code sharing .net framework project size :320 mb Whereas the same project 90% of code was only : 9mb that was a huge difference to me
Hi Tim. thanks for the great vid. I've been developing in .Net Frame for a while and was interested in redoing our website in .Net Core. I was looking on your site to check your courses. I was wondering do you have a .net core and angular 8 tutorial? Angular is still pretty new to me, not even sure what the best version of angular is good to use really. The company site is using angularjs, so i'm sure we are well behind the curve on that. Any advice would be greatly appreciated! thanks and keep up the great work!
Worth watching every second.... Grt info. And I have one doubt ,is there only two types of .net framesworks (ASP.NET and ASP.NET CORE) or do we have any other .net frameworks other than these two?
Those two project types use the .NET Framework and .NET Core. These are the two types of frameworks available. They are called ASP.NET and ASP.NET Core but that just indicates what the underlying framework is.
. NET core cross platform and open source. Basically fast branch of. NET Framework. As they don't need to keep legacy code. As you can have. NET core framework use multiple versions. Vs. You Can only have. Net framework installed once
Mostly true. The only small difference is that .NET Core and .NET Framework aren't really branches of the same framework. Not everything .NET Core gets will trickle down into .NET Framework. The reason why is because of backward compatibility.
Simplified explanation. Straight to the point. Good work. I have one question though, SQL ConfigurationManager in .Net Core; how is is achieved given that the namespace doesn't exist?
In .NET Core, we use IConfiguration in dependency injection. That is set up for you in ASP.NET Core projects. Just ask for it using dependency injection. Then you can do "config.GetConnectionString("Default");" (if you called your IConfiguration variable config).
I'm using the web frameworks to compare the differences the user will see. I discuss the difference in runtime but I wanted to get a practical comparison, not a theoretical one so I used the web frameworks as the basis.
@@IAmTimCorey I mainly thought that the title of the video was misleading as ASP.NET Core is not everything that .NET Core is. That is a product of bad marketing from Microsoft's side because they don't want to scare people who might think that they are replacing classic .NET Framework - which they in fact are doing. Supporting WPF and WinForms is a proof of that.
@@marna_li nah they're backing into the solution. they started as net core and now core is taking over as their focus since it's a more general solution
Great talk there Tim, many thanks for showing us this. I've never done Core and since the firm I work for isn't really doing "new" stuff don't think I will. :( One day I might pick it up though. The MVC project does look much "cleaner" though...
Understandable. Depending on your situation though, it might be a good idea to learn it and be ready so that when your company is ready (or if you can show a clear advantage), you are in place to lead the charge. I've done that at a number of companies that "would never move".
Very informative. As an 'oldster' (69 in May) I still like seeing what is new. And what the 'new' is in relationship to the 'old' (though not counted out, just yet [lol!]. I like that .Net Core will take 'itself' with the new deployment -- no need to have it already installed. That one is an almost 'seal the deal' type of feature (though I am sure there are others). Again very informative. Many Than(x)!!
So I've been programming since 1974 and I must say this is one of the best movies and explanations on the difference between the two technologies. It was esp nice to see an actual comparison between the two. I have decided to move off of webforms since they are no longer really supported and in all likelihood move to core. I've seen the game MS plays so many times where they make promises to continue supporting a specific language then a few years later ditch it in favor of what they deem 'better'. Watching this I know exactly what they are going to do... and what I need to do. Again fantastic job and only best wishes to you moving forward. Stay safe in this crazy world my friend.
First, you did a great job explaining .NET Core. Thank you. The following critique is only for the new technology itself, not how you have presented the information. Here goes... .NET Core strikes me as yet another "new and shiny" toy for bored developers. As both a manager and a developer for my company, I would NEVER consent to having our money-making .NET FW applications converted over to .NET Core. We control the servers (which are MS OS servers in Azure). I see no value in doing such a conversion except it indulges a developer or two on the team (who will probably end up leaving in the near future anyway -- i.e., the "bored" type I mentioned). Doing such a conversion has no value outside that. As a developer, I do see the inherent improvement in how the layout in .NET Core works (e.g., enviro setting differences -- dev versus other deployment types). As a manager, in some edge cases (for some companies) I see the cost benefit of being able to run on a cheaper server, but you ultimately have to balance that cost benefit against the cost and risk of *converting* something that works just fine in .NET FW, if perhaps a few milliseconds slower , something most users don't care about in most types of apps. Anyway, just my two cents worth. Not everyone will agree, of course.
I hear you, and if you have an application working well in .NET Framework, you are right that there isn't a huge reason to upgrade. I don't ever recommend upgrading for no benefit. The benefits need to outweigh the drawbacks. In a stable application that is mostly in maintenance mode, there aren't a ton of benefits to an upgrade. Speed is one (again, if it matters to you). New features are another (upgrading to appsettings.json and all of the other overloads for it is a HUGE improvement over app.config/web.config). Vendor support for plug-ins is another. The last major reason is the ability to find employees. Over time, the number of people who want to work on .NET is going to wane. At that point, it is going to get more expensive but you might not have a choice to upgrade then.
I like your vids... I have one question that has come up about .Net Core though, more specifically the JSON config files. I've always depended on being able to put documentation in the web.config file but JSON is specifically made not to have comments. I tend to make weird AJAX based Intranet apps so configuration is important and can change a lot. Could you suggest a way around that limitation?
Technically, you can have keys that aren't used. So something like this: "ConnectionStrings":{ "DefaultConnectionDoc": "the documentation of the Default Connection", "DefaultConnection": "" }
Good done! However I still have some questions about .NET Core deep structure. Are there any changes in translation to IL? Are .NET Core .exe and .dll files really executives and dynamic link libraries or just containers of IL code that are executed on a virtual machine? Is there still this virtual machine?
I'm a .NET developer and have been wondering what .NET Core really is and what's different or the same as what I am used to. This was a great overview. Thanks!
You are most welcome. Thanks for watching.
@Matt What does a .net core engineer do
0:00 - Intro
1:13 - Creating Framework and Core web MVC applications
4:20 - Comparing the two templates: structure
7:34 - Application settings
10:18 - Code behind controllers
14:55 - About .NET Core
17:27 - When to use one or the other?
19:28 - SDK dependency
20:26 - Clarification on Core for windows applications
21:26 - General advice and recommendations
Thanks! I just added this to the description.
Hi Ralfs or Tim, Just curious how you did it(providing the link based on the timing)? I also want to learn.
@@truptibaliarsingh5441 just write time in this format
mm:ss
UA-cam takes care of the rest.
Your cadence and voice are great. And an instructor that doesn't flick the mouse all over the screen when explaining things throwing the viewers eyes into chaos is other worldly. Very precise and thought out training. Nice one. Obviously the content is great too.
Glad it was helpful!
@@IAmTimCorey your the man.
Glad I found this video! I'm a long time .NET developer who has been avoiding .NET Core for a long time. But you showed me all sorts of things in .NET Core that I wish I'd been able to use! I'm firing up a new .NET Core project right now! Thank you!!
Sweet! I'm glad I was able to encourage you to try it out. .NET Core really does address a lot of the issues of the .NET Framework.
The speaking pace is ideal and it makes easier for new comers or who are not comfortable in English to understand easily. Thank you for the video.
You are most welcome. Thanks for watching.
I'm a native English speaker, and *I* like his pace, too. He chunks his concepts very well, too.
Taking my first steps and this clarifies alot about the technology.
Great!
I have been shying away from .NET Core up until now. Thank you so much of the nice walkthrough of the differences. It was really helpful.
Glad it was helpful!
I am used to working with ASP.NET MVC in the .NET Framework, but want to try working with .NET CORE for a new job prospect - this was just the kind of introduction I needed to get started...thank you!
Excellent!
Your videos are better than most educational content, that I have paid for.
Thank you!
Extremely well made video. Brushing up on .Net core for a job interview as I've never used it professionally. This is exactly what I needed! Subscribed :-)
Excellent!
Many thanks for best summarization .... I found it very helpful ....
You are welcome!
Very good overview Tim. Thanks for sharing
Glad it was helpful!
Visual Studio code is something of a Swiss army knife IDE. It has extensions for many languages and target environments. I had some powershell script testing to do and it could all be done in the powershell ISE, but VS code was a pretty nice interface for that as well. While working on that I noticed a series of "learn Python" videos that MS was promoting and again VS Code had Python extensions to allow development in it and adds the benefit of Intellicode assistance. It's an impressive product for free.
Yep, it is and if you stay tuned to this channel, you will see a video on working with VSCode as a C# developer coming soon.
Great video Tim, finally got around to watching this as I've not really been interested in Core before as I deal with winforms at work, however I got a project coming up for some web development and last time I did that was 10 years ago so thought I would take a look at this vid. The MVC solution looks much cleaner and easier to follow. Thanks :)
I am glad you enjoyed it.
Great video. Side by side comparison helped me understand the differences between both in an entry level. The comments are helpful too.
Awesome!
I have learnt so much about c# and .net development platform from you.Can't just thank u enough.
I am glad it was so helpful.
I am a fourth year college student, and this topic is given to me to report on class, I dont have an idea yet on both but you just saved my life. Thank You♥️♥️
You are welcome.
This sir, was a very good and informative no nonsense video. Thank you!
Glad it was helpful!
I feel that is generally Tim's style!
Hey Tim, I watched the video and I liked the way you explained it. Easy, Smooth and Simple. Thanks buddy.
Glad you liked it
Appreciate your efforts ! Wonderful explanation. Thanks
You are welcome.
my english comprehension is not the best but with your videos i understand 100%. Thanks a lot
Excellent!
@@IAmTimCorey man, do you have Domain Driven Design pattern video?
Not yet, no.
thank you, I guess this video left me with more questions. which may be more direct ones, i went from what are the differences to why is it easier? and till what point that is subjective!... thank you very much!!!
Very easy to follow comparison. I appreciate you making these videos!
Thank you!
Simple and meaningful explanation... just what I needed to know! Great video!
Thanks for trusting Tim
Very informative and most og my important questions were answered fully. Great work!
Thanks for trusting Tim for answers
an excellent overview that quickly identifies the high-level differences between .net core and framework. I'm new to both, so now when I sit down at my machine I can quickly identify which one my project is using. thanks for sharing!
Excellent!
With this rock, you have built your church. Keep with this gospel, Tim. People are learning a lot with you.
I am glad you are learning a lot.
Very clearly explained the difference between the two. Thanks !!!
You are welcome!
Great overview. Thanks
Very welcome
Thank you so much for your excellent guidance, which will significantly help me.
You're most welcome!
As an upcoming developer trying to gain more knowledge around .NET, these videos are very helpful and I thank you for that.
You are welcome.
Great comprehensive comparison! I started using .net core for new development and enjoyed the new features. Thanks a lot!
You are welcome.
His voice looks like he know every secrets of this universe
lol
Awesome explanation of the two technologies. Thank you.
You are welcome.
Wow.. Great enlightenment. I have been developing MVC apps for my firm and I was wondering what .NET Core is really like. Glad I spent my good 25 minutes learning about the differences. You are great.
Glad it was helpful!
this is completely important that you can not find out differences by just one watch
I am glad it was helpful.
My bests 25 minutes expended in months. Great, great video!
Thanks!
OK, back for round two. In round one, I made a really bone-headed comment because I mistook what Tim was doing for "Trying to do web development the long way with C# instead of taking time to learn the native languages of the browser, HTML, CSS and Javascript". Turns out, he was doing some kind of ClientServer/Desktop for native Windows code that I had no experience with, and which it turned out the the real thing he was doing was "Windows development with languages that are similar to web languages (HTML)". It was actually pretty cool, and I was totally wrong about what I was looking at. SORRY TIM. So, THIS time, I am eager to hear about .NET Core, because as an ASP.NET web developer, it looks like Core is the future.
Thanks for the comment. No need for an apology. I'm glad you are enjoying the videos. I definitely agree that .NET Core is the future.
Thanks Tim. Keep doing this for us. Debate over languages is stupid. Use what you want.
You are welcome.
Thanks a lot, Tim! Now I have no confusion.
Great!
Well explained the difference between .Net Framework and .Net Core. This video tutorial gave me a good start into understanding .Net Core. Thanks Tim for creating such a valuable piece of work.
I'm glad it was helpful.
Excellent comparison. I subscribed, thanks.
Thank you!
Excellent this explanation Tim
Thanks!
thank you
and thanks again for using a good mic
You are welcome.
this video is amazing..very crisp and clear
Thank you!
Great overview. I love your ability to explain things in a comprehensive manner.
Thank you!
Even after I completed your full course Tim, I have been using DotNet Core for about 10 months to a year. Yes there are some huge differences between the FullFramework and Core, but I find that I can have a full startup, database connection with a small running app in less than 30 minutes. Most of the time I just use Core for my API's then use something like Vue or Angular for my frontend. Works fairly well. One of the toughest challenges that I just figured out is setting up Roles and how to apply them to my users. Yes you can enable Authentication from the command line when you are create a project, but how do you do it after your project is built. That was a huge hurdle for me.
Adding authentication to an existing project is actually quite simple in .NET Core. You can right-click and add it to your project. I cover that in my Getting Started with .NET Core course. As for roles, we will be adding them in an upcoming video in the TimCo Retail Manager series so you can see them implemented there.
It was very useful session thanks man
You're welcome.
Nice video, I think .Net Core is really good, especially with Blazor, the experimental project which Microsoft is working at. Blazor will change the way web development is made now, maybe you will make a video about it? I really like it because I do not know Javascript and I should not be able to know it to do web development.
Blazor is an interesting project and I hope that it will do well. It is still quite early to do a video on it but I'm keeping an eye on it. I'll definitely do one as it gets closer to production-ready.
UniGui and Intraweb are the best web development without knowing Javascript.
You shouldn’t know it to do web development (i.e, apps that run in a WEB BROWSER)??. Lol. That’s an odd comment. Maybe Blazor will shield you from learning JS but if you know C# you should be able to write JS code wo a problem. Might as well learn it instead of learning Blazor’s idiosyncrasies. But either way, someday you’ll probably need to learn it, just like devs who used web forms were shielded from anything Web-ey (html,css,js). Then they had to learn it when MVC arrived. Round and round we go.
Just the video I was looking for.
Great!
Hi Tim ! Great presentation
Very helpful for someone who just jump in Ms code world. Seems to me very confusing at first sight to chose which MS app to use.
I took good note that .NET Core should be the framework to use from now one for www apps. That's correct ?
Regards,
Bogdan
Now that they have passed by version 4, .NET Core is now called just .NET. The current version is .NET 7. For all new applications, you want to use the latest version of .NET. I would not recommend creating anything new in the .NET Framework unless you are trying to interface it with an existing .NET Framework application.
Great explanation, always wonder the difference and couldnt find any good reference, Thank you!
Glad it was helpful!
I am .Net developer and I was kind of worried that I might have to start from scratch but I see it's the same old favourite .net with awsome improvements. Thanks for the great video
Yep, the code is practically the same, just tons of great new features (and it is really fast, too).
Another Big Difference is the project size . So i've created my graduation project in .net framework and got it almost done . Then we thought about moving it to .net core it was easy 90% code sharing
.net framework project size
:320 mb
Whereas the same project 90% of code was only : 9mb that was a huge difference to me
That's a very large project. I'm glad you saw such a drastic size reduction.
Not a one word about Startup.cs in .NET Core instead of global.asax and App_Start stuff and dependency injection support in .NET Core?
True. There is a lot more I could cover. These are some good ones.
I know, I was expecting the DI to be one of the first things, it’s a big change.
This is very helpful. Thank you.
You are welcome.
Thank you for this :"D
I was curious about it as they seemed almost identical in terms of coding so this helped a lot.
Glad it helped!
Thanks for sharing this information
You are welcome.
Thanks this is very good explanation
Thank you!
Hi Tim. thanks for the great vid. I've been developing in .Net Frame for a while and was interested in redoing our website in .Net Core. I was looking on your site to check your courses. I was wondering do you have a .net core and angular 8 tutorial? Angular is still pretty new to me, not even sure what the best version of angular is good to use really. The company site is using angularjs, so i'm sure we are well behind the curve on that. Any advice would be greatly appreciated! thanks and keep up the great work!
I don't have any content covering JavaScript frameworks. Sorry.
a short video with a lot of information
thank you
You are most welcome. Thanks for watching.
Worth watching every second.... Grt info. And I have one doubt ,is there only two types of .net framesworks (ASP.NET and ASP.NET CORE) or do we have any other .net frameworks other than these two?
Those two project types use the .NET Framework and .NET Core. These are the two types of frameworks available. They are called ASP.NET and ASP.NET Core but that just indicates what the underlying framework is.
. NET core cross platform and open source. Basically fast branch of. NET Framework. As they don't need to keep legacy code. As you can have. NET core framework use multiple versions. Vs. You Can only have. Net framework installed once
Mostly true. The only small difference is that .NET Core and .NET Framework aren't really branches of the same framework. Not everything .NET Core gets will trickle down into .NET Framework. The reason why is because of backward compatibility.
very nice explanation thank you!
You are welcome!
Thanks, Tim that was very informative. I'm new to this channel, I'm lucky that I stumbled upon.
You are most welcome. Thanks for watching.
great video tim
Thanks!
Well done. Appreciate the effort and differences. Thanks.
You are welcome.
Awesome video as always Tim!
Thank you!
Simplified explanation. Straight to the point. Good work. I have one question though, SQL ConfigurationManager in .Net Core; how is is achieved given that the namespace doesn't exist?
In .NET Core, we use IConfiguration in dependency injection. That is set up for you in ASP.NET Core projects. Just ask for it using dependency injection. Then you can do "config.GetConnectionString("Default");" (if you called your IConfiguration variable config).
cool stuff. crisp to the point. well explained !
Thank you!
You are comparing the web frameworks (app models)!!! - not the runtime frameworks.
I'm using the web frameworks to compare the differences the user will see. I discuss the difference in runtime but I wanted to get a practical comparison, not a theoretical one so I used the web frameworks as the basis.
@@IAmTimCorey I mainly thought that the title of the video was misleading as ASP.NET Core is not everything that .NET Core is. That is a product of bad marketing from Microsoft's side because they don't want to scare people who might think that they are replacing classic .NET Framework - which they in fact are doing. Supporting WPF and WinForms is a proof of that.
@@marna_li nah they're backing into the solution. they started as net core and now core is taking over as their focus since it's a more general solution
Too bad the IDE still doesn't support Form Designer for .net core...
Great talk there Tim, many thanks for showing us this. I've never done Core and since the firm I work for isn't really doing "new" stuff don't think I will. :( One day I might pick it up though. The MVC project does look much "cleaner" though...
Understandable. Depending on your situation though, it might be a good idea to learn it and be ready so that when your company is ready (or if you can show a clear advantage), you are in place to lead the charge. I've done that at a number of companies that "would never move".
How about a Entity framework Core vs EF .net tutorial.
I've got a couple EF videos like that on the list (EF Core vs Dapper is one). Thanks for the suggestion.
Dapper is dope. EE is a nightmare
I am not so familiar with Dapper. I love EE. Tell me how dapper can make things easier and better?
@@FelipeFerreira-vi2vj just watched a video and no Linq with Dapper. I love me some Linq.
Exactly!, data management is in the only thing holding us to use it
Thanks Tim, great explanation ! Will never stop learning, that's it !
Glad you enjoyed it.
Very informative. As an 'oldster' (69 in May) I still like seeing what is new. And what the 'new' is in relationship to the 'old' (though not counted out, just yet [lol!].
I like that .Net Core will take 'itself' with the new deployment -- no need to have it already installed. That one is an almost 'seal the deal' type of feature (though I am sure there are others).
Again very informative. Many Than(x)!!
Yep, it is a nice feature.
Thank you for this video. I was just asking my friend the other day that same question. :D
Excellent!
So I've been programming since 1974 and I must say this is one of the best movies and explanations on the difference between the two technologies. It was esp nice to see an actual comparison between the two. I have decided to move off of webforms since they are no longer really supported and in all likelihood move to core. I've seen the game MS plays so many times where they make promises to continue supporting a specific language then a few years later ditch it in favor of what they deem 'better'. Watching this I know exactly what they are going to do... and what I need to do. Again fantastic job and only best wishes to you moving forward. Stay safe in this crazy world my friend.
I am glad you found it so valuable.
Thank you for helpful information...
My pleasure
Thank you Tim.
You are welcome.
Amazing Work bro!
Thank you very much!
Thanks for making it clear !
You are welcome.
It's a great video! Thank you!
Glad you liked it!
Thanks for the breakdown between .NET Framework and .Net Core, a really good overview
You are most welcome. Thanks for watching.
Thanks Tim, could you upload about what is memory leak and how to resolve it in c#. It would be helpful
I will add it to the list. Thanks for the suggestion.
Very nice and quite informative !
Thank you!
Thank you!
Great explanation
Thanks for watching.
This was really helpfull! Thanks for the effort put into this video.
Glad you enjoyed it!
Hey Tim... Just need a little help...Could you please tell what's the difference between References and Dependencies?
A good video sharing some of the cool and important feature on .Net Core!!! Thanks!
You are welcome.
First, you did a great job explaining .NET Core. Thank you. The following critique is only for the new technology itself, not how you have presented the information. Here goes... .NET Core strikes me as yet another "new and shiny" toy for bored developers. As both a manager and a developer for my company, I would NEVER consent to having our money-making .NET FW applications converted over to .NET Core. We control the servers (which are MS OS servers in Azure). I see no value in doing such a conversion except it indulges a developer or two on the team (who will probably end up leaving in the near future anyway -- i.e., the "bored" type I mentioned). Doing such a conversion has no value outside that. As a developer, I do see the inherent improvement in how the layout in .NET Core works (e.g., enviro setting differences -- dev versus other deployment types). As a manager, in some edge cases (for some companies) I see the cost benefit of being able to run on a cheaper server, but you ultimately have to balance that cost benefit against the cost and risk of *converting* something that works just fine in .NET FW, if perhaps a few milliseconds slower , something most users don't care about in most types of apps. Anyway, just my two cents worth. Not everyone will agree, of course.
I hear you, and if you have an application working well in .NET Framework, you are right that there isn't a huge reason to upgrade. I don't ever recommend upgrading for no benefit. The benefits need to outweigh the drawbacks. In a stable application that is mostly in maintenance mode, there aren't a ton of benefits to an upgrade. Speed is one (again, if it matters to you). New features are another (upgrading to appsettings.json and all of the other overloads for it is a HUGE improvement over app.config/web.config). Vendor support for plug-ins is another. The last major reason is the ability to find employees. Over time, the number of people who want to work on .NET is going to wane. At that point, it is going to get more expensive but you might not have a choice to upgrade then.
neat comparison, thanks!
Glad you liked it!
Well explained, Thx
You are welcome.
I like your vids... I have one question that has come up about .Net Core though, more specifically the JSON config files. I've always depended on being able to put documentation in the web.config file but JSON is specifically made not to have comments. I tend to make weird AJAX based Intranet apps so configuration is important and can change a lot. Could you suggest a way around that limitation?
Technically, you can have keys that aren't used. So something like this:
"ConnectionStrings":{
"DefaultConnectionDoc": "the documentation of the Default Connection",
"DefaultConnection": ""
}
@@IAmTimCorey Thanks a lot!!! I've just started working with JSON config files so I didn't figure that out.
Great video, thank you
Glad you liked it!
Very informative. Also great speaking skills - not speaking too fast and making sure to enunciate words. Thanks!
Thank you!
Thanks for you this quick video.It help me to understand.
You are welcome.
You man! you are the best !!!
Thank you!
Do you have a video teaching how the pipeline works? I am a little confused by it.
What pipeline are you referring to?
@@IAmTimCorey The .Net core middleware pipeline
So basically, every additional folder shown in the full framework project can be subsumed in the "wwwroot" directory?
The full framework doesn't have a separate wwwroot directory.
Good done! However I still have some questions about .NET Core deep structure.
Are there any changes in translation to IL?
Are .NET Core .exe and .dll files really executives and dynamic link libraries or just containers of IL code that are executed on a virtual machine?
Is there still this virtual machine?
There is still the VM, I believe. It is just cross-platform, smaller, and faster.
@@IAmTimCorey , thank you.