Which Version Control Solution Should You Use?

B

Git history: File history is replicated on the client dev machine and can be viewed even when not connected to the server. You can view history in Visual Studio and on the web portal.

Note: Azure Repos supports two types of version control: Git and Team Foundation Version Control (TFVC).

Incorrect Answers:

A: Team Foundation Version Control: File history is not replicated on the client dev machine and so can be viewed only when you're connected to the server.

Given that multiple developers will work on the project and they will need access to the full project history while they are offline, the most suitable version control solution is Git.

Git is a distributed version control system that allows developers to work collaboratively on a project without relying on a central server. Each developer has a local copy of the repository, which they can work on and make changes to, even when they are offline. When they are ready to share their changes, they can push them to a remote repository, where other developers can pull the changes and incorporate them into their own local copies of the repository.

In contrast, Team Foundation Version Control (TFVC) is a centralized version control system that relies on a central server to store the repository. Developers must have access to the server to check out files and make changes, and they cannot work offline without first checking out files and creating a local workspace. While TFVC does offer some offline capabilities, it is not as flexible as Git in this regard.

TortoiseSVN and Subversion are both centralized version control systems similar to TFVC, and do not offer the same level of flexibility for offline work as Git does.

Therefore, the correct answer is B. Git.