Drag and Drop Question You have an Azure DevOps project that has Dev and Test branches. The Test branch is used for deploying artifacts in a test environment. You must merge code from the last Dev…

Question

Exhibit

Answer Area

Explanation

Azure DevOps TFVC Branch Merge - Order Explained

This question is about TFVC (Team Foundation Version Control), not Git. The workflow uses Visual Studio's Source Control Explorer to merge from Dev into Test.

Why This Order?

1. Connect a Visual Studio workspace to an Azure DevOps project.

You cannot do anything else without first establishing a workspace connection. A workspace is the bridge between your local machine and the remote TFS/Azure DevOps server. This is always the prerequisite - no connection, no access to any branches.

2. Map the Test branch to a local folder on your machine.

Before you can work with a branch in TFVC, it must be mapped to a local directory in your workspace. Without a local mapping, the branch has no physical presence on your machine and you cannot right-click it in Source Control Explorer - the context menu options simply won't be available. You map Test (the target) because that's the branch you'll be working in and checking code into.

Common misconception: People assume you need to map the Dev branch since that's the source. In TFVC merge workflows initiated via Source Control Explorer, you right-click the target branch, so the target (Test) must be mapped.

3. Right-click the Test branch and select Merge.

Now that Test is mapped locally, you can right-click it in Source Control Explorer and choose Merge. This launches the Source Control Merge wizard. The branch you right-click determines the target of the merge - this is how TFVC knows where the result will land.

Common mistake: Right-clicking Dev instead of Test. If you right-click the source branch, the wizard defaults to merging from that branch, which reverses your intent.

4. In the Source Control Merge wizard, set the target branch to Test.

Once the wizard opens, you confirm (or set) the target branch as Test. Even though you right-clicked Test, the wizard allows you to verify and configure both source and target. The source should automatically be Dev (the last Dev branch), and the target should be Test. This step locks in the merge direction.

5. In the Source Control Merge wizard, select Selected changelists.

This is the final configuration step before executing the merge. "Selected changelists" lets you cherry-pick specific changesets from Dev rather than merging everything - appropriate here because the question says "merge code from the last Dev branch," implying a specific set of changes, not the full history.

Common misconception: Choosing "Latest version" seems intuitive, but "Selected changelists" gives you precise control over which Dev changes flow into Test, which is the correct approach when targeting a specific set of changes.

Key Takeaway

The order follows a strict setup → access → initiate → configure → specify pattern. Each step is a hard dependency on the previous one: you can't map without connecting, can't open the wizard without mapping, and can't configure what you haven't opened.

No community discussion yet for this question.