Visual Studio 2017 has a completely new installation experience, allowing you to dial in just what you need to install. Learn about the new workspaces feature of VS2017 and what you need to install for .NET Core. Installing and updating the .NET Core SDK and verifying the version installed is covered.
- [Instructor] If you haven't yet installed Visual Studio 2017 and .NET Core, the installation experience is a little bit different than prior versions. The installation process is now divided into workloads. Now, this is similar to prior versions of Visual Studio where you could choose web developers or C Sharp Developer, which is much more refined and granular. So from the screenshot here, you can see there's ASP.NET development, there's no Jsers, there is different tasks.
And what we'll do for you, is then install the components you need to do that type of work. So let's pull up the installer and look at it. So I have installed Visual Studio Enterprise, there's also Visual Studio Community and Visual Studio Professional, and it's all launched from the same installer. I've already installed it, let's go into Modify to look at the different workloads. So you can see there's Universal in this platform, .NET desktop and many others.
But we want to make sure we have selected ASP.NET and web development and then we'll install ASP.NET Core. And then scroll down to the very bottom and also pick .NET Core cross platform development. One other thing we want to check is go to Individual Components and make sure that .NET Core runtime is selected as well. I've already installed it, so there's nothing for me to do, but you would just click install. It'll also tell you the size on disk of the installations that you have selected.
Now, .NET Core also gets us to Visual Studio 2017 and we want to confirm that it did get installed. And we can do that very simply with the command prompt. You want to confirm that .NET Core is installed. And we first type in just the command dotnet and it shows us that we have the one point one Shared Framework Host installed. We can also dotnet dash dash. Info says that the command line tools are one point zero one.
It's a little confusing with the different version numbers. The command line tools are what I just ran. Dotnet, we can dotnet run, dotnet EF, migrations, we'll see all this later in the course. So we have the SDK, but also have the shared framework host. And then we can also do dotnet dash dash version and it is also one point o one. What you don't want to see here is RC. If you've been using some of the earlier versions, you might still have an RC installed.
If you need to update to .NET Core runtime, or SDKs, Microsoft has set up a very convenient website to get everything that you need dotnet. The URL is very, very simple. Www.dot.net. And that will re-direct you to this page. Here you can download Visual Studio, .NET Core, and well, pretty much everything in the .NET space, not just Core, but four point six and the old frameworks and everything else.
What you want to do is click on Download, go to .NET Core. And then on this page, you can download everything that you need, one point o and one point one. The SDKs or the runtimes for both Windows versions, x64 and x86, Mac, Linux, and Visual Studio.
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