TFS - defining an assembly with a frequently changing route

Question

My team uses a branching approach for every spread. Thus, we usually have a new Main branch (integration) for the current sprint and a Main branch for each version.

Main Branch
|
 -- Development Folder
|   |
|   -- Sprint 2.10_1 Branch
|   -- Sprint 2.10_2 Branch   *current*
|
 -- Release Folder
|   |
|   -- Release 2.8.0 Branch
|   -- Release 2.9.0 Branch   *current*

There are two definitions of construction. One moment points to the current dev branch and other points in the current release branch.

This setup works well, except that it has become a little time-consuming and error prone to update all branch paths in assemblies every time we keep a branch for a new sprint and a branch for a new version. Each assembly has path branches in these places:

• Source settings> source control folders (several active and hidden paths)

• Process Settings> Build> Build Projects (Paths to Multiple Projects)

- tfs, , , - , . , , /developement/2.10_1//developement/2.10_2/.

, ? , , , ? , , ? ?

, ?

? !

Answer 1

, $(BranchToBuild), . , " " .

, /p:BranchToBuild=2.10_2 " ", , .

, /p:BranchToBuild=2.10_2 . , , "", , ( , , )

- ( ), , . , (10.1_1) . , , . 10.1_1 10.1_2, . , .

, 30 .

, vcproj, , , . . , , , , , vcproj. , , , 7 .