The introduction of ASP.NET Core is a game changer for .NET web developers, and ASP.NET Core 2 contains more excellent and significant changes. This course will get you ready to start building applications with version 2 of this marvelous framework.
Understanding ASP.NET Core 2.x is suitable for developers that are new to ASP.NET Core, as well as for those who have worked with earlier versions. In this course, Understanding ASP.NET Core 2.x, you'll be provided with everything you need to know in order to build ASP.NET Core 2 applications. First, you'll explore the csproj project structure, while you setup the pipeline with middleware and configure dependency injection. Next, you'll learn about NuGET, NPM and Bower packages, task runners, as well as the light-up feature. Then, you'll delve into environments, controllers, tag helpers, application settings, and view components in action. Additionally, you'll discover how to create a REST based Web API, along with exploring how .NET Core works with .NET Standard, CoreFX and CoreCLR, and the DotNet CLI (.NET CLI). Finally, you'll deploy to IIS, Azure Web Apps, and Linux using a self-contained or framework-dependent deployment. By the end of this course, you'll have the necessary skills and knowledge to confidently build ASP.NET Core 2 applications.
Course Overview Hello. This is Ronald Guijt. Welcome to my course on ASP. NET Core 2. It doesn't matter if you have used a previous version of ASP. NET Core or not, this course will get you ready to start building with this marvelous framework. We'll start with an empty project and build a business application from the ground up. On the way, I'll explain everything you have to know about. NET Core 2 and ASP. NET Core 2. The major topics of this course are exploring the new project structure, showing you that dependency injection is now essential, that middleware lets you create your own pipeline, and all the ins and outs about the new metapackage; working with packages and libraries, the different package sources that are now supported, how to bundle and minify, and the new light-up feature; understanding ASP. NET Core 2 MVC, showing off some great new additions to MVC such as tag helpers, view components, and unified controllers; setting up a web API, letting you create a REST-based web API using the exact same classes used in MVC; developing applications across frameworks and operating systems. In here, I'm explaining how. NET Core works, also together with the. NET platform Standard. And finally, deploying ASP. NET Core 2 applications where we will see that it is now possible to run your app on many different operating systems without the need to preinstall. NET Core. I assume that you have experience using a previous version of MVC, as well as knowledge about HTML and web programming in general. After watching this course, you will be able to start building ASP. NET Core 2 applications while understanding what makes it tick.
Working with Packages and Libraries This second module is entitled, Working With Packages and Libraries. We're going to take a look at the various package sources that are available to you. You'll also see how to create some simple bundling and minification tasks for our demo app with the built-in bundling and minification feature. Next, we'll take a look at more advanced task runners, like gulp, grunt, and webpack. ASP. NET Core 2 makes it easy to reference all their full. NET Framework packages; I will show you how. And finally, the light-up feature seems like magic when you see it for the first time. I will show you what it is and how it works. But first, the different package sources.
Understanding ASP.NET Core 2 MVC In this module I'm going to build most of the demo app using MVC for ASP. NET Core. You'll see how to set up MVC in a new project. Environments help you to distinguish between development, staging, and production. Controllers in MVC are unified, and you will learn what that means. Tag helpers are great to render tags in a very HTML-friendly way. I will show you the new way to do application settings, and view components are partial views on steroids. You'll see how that works as well.
Setting up a Web API This module is about creating and accessing a web API with ASP. NET Core. We're going to change the architecture of the app. I'll start by showing you how. Then I'll talk about why you will want a web API. Next, some theory about REST, after which I'll show you how the web API is implemented. A cool feature of web APIs is that they can support multiple formats, and I will show you how to try the web API out and how to access the web API from a. NET app, in our case, the Globomantics web application.
Developing Applications Across Frameworks and Operating Systems Where the previous modules were more hands on, this module contains a bit more theory. You'll learn what the roles of the full. NET Framework,. NET Core, and the. NET Core CLI are, and it will also become clear why. NET Core applications can run cross-platform where full. NET Framework applications cannot. In a moment I will start by explaining how the. NET Framework developers have used since the beginnings of. NET works. You will also learn about Mono and. NET Core and how they are different from the traditional framework. Code sharing is done using the successor of PCLs, a. NET Platform Standard, and I will give you some guidelines helping you to decide which framework to use. Lastly you will see how the. NET Core CLI runs your ASP. NET Core application.
Deploying ASP.NET Core 2 Applications This module is about deploying ASP. NET Core applications. First, I'll go into the differences between Framework-Dependent, or FDD, and Self-Contained, or SCD, deployments. Then you'll learn what Visual Studio does when you publish a framework-dependent app. After that, two excursions about the runtime store and Kestrel and native dependencies. That knowledge will come in useful when we're going to take a look at publishing a self-contained app. Next I'll show you how to deploy to different operating systems, first IIS and Windows, then Microsoft Azure, and finally, Linux. After that you can practically deploy to any supported platform because the basics are the same every time. But let's start with the differences between framework-dependent and self-contained deployments.