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!
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!!
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
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♥️♥️
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 :-)
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!
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.
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.
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 :)
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.
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!
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.
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.
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)!!
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 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
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.
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".
One thing that would be extremely helpful is at the outset saying something like "In 2020 nobody should learn .NET Framework anymore,. .NET Core is here to stay and is the future". Also, it would be helpful to change the title of the video 'Transitioning from .NET Framework to .NET Core -- What are the differences?". Believe it or not, some people (who have experience using .NET) don't have a big picture view of the myriad of Microsoft platform releases.
Well, the thing is that I don't really agree with that first statement. Learning .NET Framework is the same as learning .NET Core in about 95% of all cases. The C# code works the exact same way from a functional standpoint. So there is no reason to throw out all .NET Framework learning. Also, while .NET Core is the way to do NEW projects, the key to remember is that there is a LOT of legacy applications out there. If you hire on to a company (that isn't a startup), the odds are you will be working with the .NET Framework. Major applications don't just transition to .NET Core because it is the new thing. It takes a LOT of planning and preparation. I know many people who are using WinForms and ASP WebForms for development currently because that is what their system was designed on originally and it would be too expensive to move it over.
@@IAmTimCorey OMG thank you for the explanation!!! That's exactly the information that everyone assumes we know, but we don't. I am still using WebForms (which by the way are far easier and more accessible) and thought I could just "jump over" .NET Framework. Thank you for explaining that I can't really do that. However, I kind of don't want to have to learn legacy things like @ViewBag and @Html instead of Tag Helpers. Do you have a course that can bring me up to speed so that I can quickly move to .NET Core 3.x? I am fine with paying as long as there's a reasonable expectation that someone with almost no experience in MVC can understand it.
Is there a difference between "Framework" (in New project/ Configure) and "Target framework" (Project, Application properties)? The word "target" in database world is a target server, different than the source server. That concept doesn't apply re: Frameworks. Whatever F version was used (or possibly versions were used) in development determines the executable application. So then why use the term "Target framework"?
This video is pretty disappointing, has nothing to do with the title. You just go through the differences of how an MVC application is structured in .NET Core vs .NET Framework and a few differences, but only related to web applications, not the actual, global differences between the two. You should rename it to "Comparing an MVC application in .NET Core vs .NET Framework" or something like that, so people won't waste 30 minutes.
This video is a comparison of the practical differences between how .NET Framework code is written vs. .NET Core code. It uses MVC as a comparison because there is an MVC template in each (apples to apples). That is just the framework for the discussion. As for only relating to web applications, right now that is what .NET Core is mostly about (that and Console apps, which changed even less). .NET Core 3.0 will have desktop app support (not cross-platform though) but that is a long way from general availability. So comparing those wasn't a fair comparison. If you expected me to go into the behind-the-scenes of the language, that really is out of scope for this channel. I focus on practical, real-world development. Knowing the architectural differences between the two could be interesting, but you can't really do anything with it. I teach people how to do something with what I teach.
@@jasper5016 If you don't like seeing opinions that you disagree with, don't read the comments. I'd rather someone tell me what the video is about than have to just hope that I don't waste my time watching something useless.
