ASP.NET Core has been updated to a 2.0 version and has many differences that will be covered here. In this course, Upgrading Your ASP.NET Core 1.x Web API to 2.0, you'll learn how to upgrade your existing web API, built with ASP.NET Core 1.x, to ASP.NET Core 2.0. First, you'll discover what these changes are and how .NET Core 2.0, the .NET Standard 2.0, and ASP.NET Core 2.0 are related. Next, you'll explore how to upgrade your existing project files and references to support new features like the run-time store. Finally, you'll learn about what you can change in regards to your code to make use of new ASP.NET Core 2.0 functionality. After this course, your existing ASP.NET Core 1.x web API will be fully upgraded to ASP.NET Core 2.0.
Course Overview Hi, I'm Kevin. Welcome to this Pluralsight course, Upgrading Your ASP. NET Core 1. x Web API to 2. 0. I'm a solution architect focused on APIs and security, and a Microsoft MVP. As you've guessed from the course title, this course focuses on the upgrade process for Web APIs between version 1. 0 and 2. 0 of ASP. NET Core. Over the course of three modules, you'll learn all about the differences between ASP. NET Core 1. 0 and 2. 0 related to building APIs. We'll start by looking into the reasons you might have for upgrading, or to hold off on upgrading. We'll dive into the. NET standard,. NET Core, and ASP. NET core, and we'll learn how they are related. We'll cover self-contained versus framework dependent applications, and we'll cover the new features ASP. NET Core 2. 0 offers, like the Microsoft. AspNetCore. All metapackage. You'll learn about changes related to tooling in the project system, but you'll also learn how to improve parts of your code when using ASP. NET Core 2. 0. At the end of this course, you'll know how to upgrade your existing API to ASP. NET Core 2. 0.
Introduction to ASP.NET Core 2.0 Hi there, and welcome to the Upgrading Your ASP. NET Core 1. x Web API to 2. 0 course at Pluralsight. My name is Kevin, and I'll guide you through it. In this first module, we'll start out with prerequisites and required tooling for this course. Then, we'll see how we got to version 2. 0, and where we're coming from. We'll shortly check out what's new in ASP. NET Core 2. 0 in regards to building APIs, and we'll learn why you might or might not want to upgrade. As it's so important, we'll also cover exactly how. NET Core 2. 0, ASP. NET Core 2. 0, and the. NET Standard 2. 0 are related. After that, we'll check out the requirements for upgrading to ASP. NET Core 2. 0, including a demo on how to fulfill them. If you happen to have any questions, the best place to post them is on the Discussions tab on the course page. I check this regularly, and like that, the questions and answers can help other people out as well. For very short questions that require a quick answer, you can contact me on Twitter. I also tweet out info on my upcoming courses, user group events, and regular technical links. Let's start with those prerequisites.
Upgrading Your Project Files & References Hi there, and welcome to the Upgrading Your Project Files and References module from the Upgrading Your ASP. NET Core 1. x Web API to 2. 0 course at Pluralsight. My name is Kevin, and I'll guide you through it. As the title implies, this module is all about upgrading our project file and references to ASP. NET Core 2. We'll learn how we can target. NET Core 2, and what it means in relation to ASP. NET Core 2 as far as package references are concerned. We'll check out two new ASP. NET Core 2 features, the Microsoft. AspNetCore. All metapackage, and the runtime store, and specifically why they were added, and which problems they aim to solve. That'll bring us into looking into self-contained applications versus framework dependent applications, and the effect those two concepts have on that. Lastly, we'll also look into some important additional project file tag differences. But let's start with introducing the demo application.
Upgrading Your Code Hi there, and welcome to the Upgrading Your Code module from the Upgrading Your ASP. NET Core 1. x Web API to 2. 0 course at Pluralsight. My name is Kevin, and I'll guide you through it. In this module, we'll look into the code changes we can or have to make to our ASP. NET Core 1. 0 API. And there's actually very few of these that we have to do. About 95% of our demo code can just remain as is. The improvements ASP. NET Core 2 brings aren't that much related to existing code as they are to new code you might write when using the extended API service. We'll start by inspecting the changes to the Bootstrapping process. More specifically, what CreateDefaultBuilder does to the bootstrapping process. We'll notice that ASP. NET Core 2 brings with it some default setup for, and changes to, logging and configuration. So that means we'll have to change a few things in our Program and Startup classes. We'll also notice that these changes can have an effect on the tooling used by Entity Framework Core 2, so we'll also look into those. Let's start by inspecting the changes to the bootstrapping process.