Use the Visual Studio Installer to add new tools and features when needed. This video examines how to customize the install using the Workloads and Individual Components tabs.
- [Instructor] In this video, we are looking at a computer that only has the Visual Studio core editor bits installed. I'm ready to add some functionality to Visual Studio, so I open up the Visual Studio installer and there are two ways to add features. I can go to the Workloads section or the individual components. I'll start by looking at individual components. Now these are the smallest pieces that you can add to Visual Studio, and they're broken down by categories. First category is .NET, second category is cloud, database, and server, then we have code tools, compilers, build tools, and runtimes, debugging and testing, something that Microsoft calls development activities, emulators, games and graphics, and then finally we have SDKs, libraries, and frameworks.
So you can look through this list of individual components and pick one of these items to add. So that would be adding a single item to the Visual Studio install. For example, let's say I want to add the TypeScript 2.1 SDK. Click here, and you'll see that a checkmark shows up, and then over here on this side of the screen you'll see that the install size is 14 megabytes. So this'll be a lightning fast install because it's only installing this one small SDK.
To uncheck an item, you can go to one of the two places. You can go over here to the individual component, this, or, you can go over here to what's called the summary screen and here is where you see all the individual components that you've selected. In this case, there's only one at the moment. I can uncheck it here, too. Now for this example, I want to add some tools to Visual Studio. So I'm looking in this section here called code tools.
One of the tools that I wanted to add was this GitHub extension for Visual Studio. So I click here and you see again I get the individual components list over here. Now some of these items have dependencies. For instance, I might want to add this thing called the Code Map. This is a feature of the Enterprise edition. So when I checkmark this one, the installer knows that there's some dependencies here. I need to have the DGML editor, the SQL Server Native Client, SQL Server Express LocalDB, and the Code Map.
The nice thing about the summary is you don't have to move up and down and look through this long list to see all the individual components that you're installing. They're listed here in the summary section. Now when I go to remove one of these items, let's say that I decide to remove this DGML editor, the installer knows that there's a dependency there and it's telling me that the Code Map feature depends on this DGML editor, so would I like to remove Code Map too? So same thing when I try to remove the SQL Server Native Client.
It says that the LocalDB has a dependency on this so I'll remove both of those. So that's what you see here in the individual components. Microsoft also is thinking about how to add groups of components by having something called Workloads. The way you can think of workloads is what kind of development work do you as a developer want to do with this copy of Visual Studio. And they break them down by large categories. For instance, what if I am a web developer.
I know I want my web development tools, so I would check this checkbox. Then let's go back and look at the individual components, you'll see that there's a large number of individual components selected here. So this is a quick way of toggling on and off a group of components that you need. And if you look at the summary list you'll see here's what we're going to get. With web development, we're going to get .NET Framework installed, 4.6.1, some web development tools, and some Developer Analytics.
And then there's also a list of optional features here. Some of them are selected, some of them are not. So let's say I don't want Docker, so I'll uncheck that, and I do want to have support for F#. So I've modified the Workload that Microsoft has suggested. Now let's say as a web developer I also realize that I need to do Azure development, so I'll come over here and click that and then I also want to do Node.js, so I'll select this one too. And now you see I've got four areas over here.
Web development, Azure development, Node.js development, and the core, and I haven't added anything to the core so that's empty. And now I've got a summary of 6.4 gigabytes for this install. So the takeaway from this is that you can customize your copy of Visual Studio anytime, and if you know down to the individual component what you want to install, just choose it from this tab. If you just know the general type of development that you want to do, then choose the appropriate Workload.
- Installing Visual Studio 2017
- Using debugging features
- Reviewing document navigation enhancements
- Examining IntelliSense Improvements
- Using XAML tools
- Reviewing the tooling added to support Docker containers
- Debugging without the hosting process
- Using the Visual Studio 2017 Installer