Join Walt Ritscher for an in-depth discussion in this video Notes for Visual Studio 2017 developers, part of Visual Studio Essential Training: 10 Protecting Your Code Base with Source Control Providers.
- [Instructor] The source control tools in Visual Studio get updated on an infrequent cadence. Every four or five years they get a makeover, because trends in the software industry demand a revised approach to working with source control systems. For example, the continued migration to get impacts developers and their tools. This course looks at source control tooling in Visual Studio. The examples in this course are shown in Visual Studio 2015, but most of the tools in the IDE are untouched in Visual Studio 2017.
Sure, there are some cosmetic changes, some menus have been retooled, the team Explorer has some rearranged UI in some areas. These are minor changes, and easily grasped. So, if you are a Visual Studio 2017 user, most of this course is applicable to your IDE, too. Having said that, I'd like to look at a few areas that are different, or might be confusing. I'll start here by looking at Visual Studio. On the left side of the screen, I've got Visual Studio 2015, and on the right, I've got 2017.
As you can see here in the Team Explorer, which is where you go to work with your source control repositories, the homepage on both these IDEs is identical, but there are some changes when you start looking at things like connections. So, I'll click on manage connections on 2015, and then manage connections on 2017, and you can see there's some minor differences here. This is called hosted service providers. And, when you click on manage connections, and connect to a project, you can start to see some differences.
This UI on the right is dramatically different from the one over here. Over here, I select the server, and then this is the logon screen here, I have to login to my account. But, the point is, there's some minor differences in the way you look at some of the tooling in 2017, but for the most part, the lessons are exactly the same. During the course, I install and demonstrate a source control add-in that enable support for the mercurial source control system. In Visual Studio 2015, I use the VisualHG add-in.
It hasn't been updated for Visual Studio 2017, so there is a comparable add-in here, called HgSscPackage that you can install to follow along. The UI will be slightly different, but the basics are the same. There's another change that affects the course, and it's over here on the Visual Studio website. As is the case for most web tools, the UI and features available have gradually changed each month. So, when you login to the site, the main page will be different. When you switch over to your account, and looking through my information page, it might be different when you navigate to one of your team projects.
You'll see some difference in here in the way Microsoft has arranged the menus on the page. And a lot of your UI for looking at the team members, and adding and removing items from your teams is slightly different. Be aware that all of the features shown on this site are still available. You may have to do some detective work to match the current pages on the site with what is shown in the course. Protecting your code base with a source control system is vital, you know that. You wouldn't be taking this course otherwise. The general principles demonstrated in the videos are timeless.
With a few small adjustments, the lessons in the course apply to Visual Studio 2017, and you.
- Source control principles
- Signing up for Team Services
- Creating team projects
- Adding projects to source control
- Checking in and checking out changes from the repository
- Adding users to a team project
- Tracking work items
- Adding projects to Git
- Using history to understand team commits
- Using tags to label versions
Skill Level Beginner
Q: This course was updated on 08/23/2017. What changed?
A: A new video was added that provides notes for Visual Studio 2017 developers.