Overview
-
Explore the source control options in Visual Studio, including Team Foundation and Team Services. Learn how to prevent accidental overwrites, enable rollbacks, and resolve bugs.
Syllabus
-
Introduction
- Welcome
- What you should know before watching
- How to use the exercise files
- Install Visual Studio
- Install the Git and GitHub extensions
- Create a Visual Studio Team Services account
- Work with multiple users in the exercise files
- Notes for Visual Studio 2017 developers
- Source control and team workflows
- Principles of source control
- Source control providers
- Source control from the IDE
- What are Team Services?
- Sign up for Visual Studio Team Services
- Create a team project
- Create another team project
- Explore team projects in the browser
- Connect to Team Project in Visual Studio
- Configure a workspace
- Add a new project to source control
- Add an existing project to source control
- Check in changes to the repository
- Check out items from the repository
- Option settings for solo developers
- Rename, move, and other operations
- Get a specific version of changeset
- Use a label to indicate versions
- Add users to a team project
- Connect another user to Team Services
- Open a project from source control
- Change a project from a second team member
- CodeLens
- Use the diff tool to compare files
- Use the diff tool to compare folders
- Use a Shelfset to suspend work
- Overview of work items
- Track bugs and issues with a work item
- Add tasks with a work item
- Examine my work items
- Query work items
- Work with the web portal
- Create a new project with Git as source control
- Add an existing project to Git
- Survey the Git host providers
- Create a Git-based team project on Team Services
- Publish repo to Team Services
- Publish repo to GitHub
- Publish repo to BitBucket
- Understand forking and GitHub collaborators
- Clone remote repo to a local repository
- Work with files in a local repository
- Use history and diff tools to explore changes
- Sync changes to remote with push, pull, and fetch
- Use history to understand team commits
- Use tags to label versions and milestones
- Next steps
