You've heard the talk, watched a few intro videos, and browsed the docs. Now it's time to move your existing web application into ASP.NET Core. In this course, you'll learn step-by-step exactly how you can port current ASP.NET applications over to the new and improved ASP.NET Core stack. First, you'll explore how to setup your request and responsive pipeline. Next, you'll discover how to consume and create services such as Entity Framework. Then, you'll jump to working with the new HttpRequest and HttpResponse objects. Finally, you'll learn how to use server features to ensure your code can run on any platform. By the end of this course, you'll know how to migrate your existing legacy ASP.NET applications, or to get a better handle at some of the inner workings of ASP.NET Core from the context of a legacy application.
Course Overview Ah, yes. ASP. NET Core. You've probably seen all of the file, new project demos, maybe watched a few recorded talks on how ASP. NET Core is the latest and greatest thing to happen to web development. Microsoft has pretty clearly stated that ASP. NET Core is the future of web development, as far as they're concerned, and they're expecting all web devs to get on board. But now what? My name is Chad McCallum, and I'd like to introduce you to my course, Migrating Legacy HTTP Modules and Handlers to ASP. NET Core. That might sound like a mouthful because, just like the course, there's a lot of content here. All of the demos in this implementation-heavy course are based on existing legacy ASP. NET applications and show you step by step exactly how you can port current ASP. NET applications over to the new and improved ASP. NET Core stack. We'll be covering all of the important parts, including setting up your request and response pipeline, consuming and creating services such as NTB framework, moving to the new configuration system, working with the new HttpRequest and HttpResponse objects, and using server features to ensure your code can run on any platform. This course is meant for developers who are somewhat familiar with the concepts and ideas behind ASP. NET Core and are looking for the next step to migrate their existing legacy ASP. NET applications or even just to get a better handle of some of the innerworkings of ASP. NET Core from the context of a legacy application. I hope you'll join me as we work our way through migrating legacy HTTP modules and handlers to ASP. NET Core, here at Pluralsight.