This section discusses the prerequisite for this class, both development knowledge and software.
- [Instructor] This course assumes that you know Visual Studio and C# 6.0, ASP.NET Web API 2.2, and a little bit about Entity Framework 6.x. Software required for this course is Visual Studio 2017, any version. The Community Edition, which is now free, is fully capable of handling everything that we are doing in this course, and that can be downloaded from the URL on your screen.
You should also have SQL Server Express 2016 on your machine. This is also a free product, and when you install that you get SQL Server Management Studio which makes it much easier to work with databases. LocalDB is a version of SQL Server Express and gets installed with Visual Studio 2017. So you don't technically need SQL Server Express, but it is a nice tool for working with databases instead of trying to work with them inside of Visual Studio.
I want to take a little bit of time to talk about the .NET Core Support Lifecycles as that might affect your decision on which version to work with in your production applications. You're going to hear a couple terms when you're working with .NET Core. Long-Term Support is sometimes referred to as LTS, and current. This is a little confusing because the LTS version is also the current version, but LTS refers to the major release so the 1.0, 2.0.
They're only going to get upgraded with critical patches. So for example, 1.0.1 or 2.0.1, and they are supported for three years after general availability or at least one year after the next major version release, also known as the LTS. The current version, which is what we will be working with in this course, refers to the minor releases, so 1.1 or 1.2. They're upgraded more rapidly, and they're supported for three months after the next current release.
Now this is a little confusing, as Microsoft licensing always is, but rest assured that your current version is supported for three years as long as you keep your major and minor versions current. So when 1.2 gets released, you'll need to upgrade to that. For all of the gory details of the support lifecycles, just go to the URL on your screen, and it has all of the information that you'll need to know before you release any .NET Core application into production.
- Creating the .NET Core project
- Adding Entity Framework
- Migrating the data access layer (DAL)
- Configuring services and the HTTP pipeline
- Adding remaining services to the dependency injection container
- Migrating controllers and actions
- Testing the services