This course requires Visual Studio 2017—any edition—and SQL Server 2014 or above—any edition. The Community Edition of Visual Studio 2017 is free—with certain restrictions—and SQL Server Express is also free. It is helpful if you already know C#, and have at least an introductory knowledge of ASP.NET MVC and Entity Framework (EF).
There's some software that you'll need to have installed. It's a pretty short list. Visual Studio 2017, and that's any version, community, all the way up to enterprise. Community is free, so if you don't own a Visual Studio, you can certainly download it for free from visualstudio.com. The .NET SDK needs to be installed in the "current" version, and "current" is in quotes 'cause it has a very specific meaning which we'll cover on the next slide. That can be downloaded from www.dot.net.
It's a pretty clever URL. And as a side note, you can also get the Visual Studio from dot.net as well. And the final piece of software, not absolutely mandatory but helpful because you get to client-side tools, is SQL Server Express 2016. Were' actually going to be using LocalDB which gets installed with Visual Studio 2017. But I'm going to ask, for simplicity, that you install 2016 and that's available at the URL at the bottom of your screen.
That also is free. Now, if you are running SQL Server Express 2014, this course will work, but the connection string will have to be different and we will cover that in a later module. Now, I've mentioned that "current" was in quote, and that it had kind of a special meaning, and it does, so the Support Lifecycles for .NET Core are a little different in previous versions of Microsoft software. The Long-Term Support version or LTS, as you'll see it referenced on the web, revolves around the major releases, as in 1.0, 2.0 and et cetera.
They only get patches with critical fixes. So, for example, right now, the LTS version that is in production right now is 1.03. The Support Lifecycle is the standard Support Lifecycle three years after GA, or at least one year after the next major release. The "current" version is what we are going to be working with in this course. And the "current" version reflects minor releases, so the dot releases as they call them, 1.1, 1.2, et cetera.
They are upgraded more rapidly but they are not supported nearly as long. So a "current" release is supported for three months after the next "current" release. Of course, there's a lot more fine print if you're going to be rolling any .NET Core applications to production and I highly recommend that you visit the URL at the bottom of your screen and get all of the details about the Support Lifecycles.
Phil Japikse begins by showing how to install and update the .NET Core SDK. He reviews the functionality of the MVC 5 app, explains how to create necessary projects, and discusses migrating static content. Next, he demonstrates how to create a data access layer, complete the server-side migration, set up the HTTP pipeline, add custom items into the dependency injection container, leverage the new project configuration system, and migrate the controllers. Phil then introduces Tag Helpers—one the big new features in ASP.NET Core—and uses them to migrate and simplify the views. Phil also demonstrates how to create and use custom Tag Helpers. To wrap up, he covers working with view components, explaining what they are and why they're helpful. He walks through how to create the server-side view component code, and how to refactor your app and invoke the view component.
- Reviewing the MVC 5 application
- Creating the data access layer
- Adding and updating the models
- Updating the database
- Completing the server-side migration
- Configuring the HTTP pipeline
- Configuring and using dependency injection
- Migrating the views
- Creating view components