This project has moved and is read-only. For the latest updates, please go here.

Why does the file reference path changes after branch merging

Sep 2, 2011 at 11:01 PM

I add a file reference to a project in the RELEASE branch. The reference properties are...

Copy Local = true

Path (read-only property) = C:\Projects\Framework\Files\Assemblies\Release\test.dll

Everything else is the default.


Then, I check-in the project into the RELEASE branch. I merge the changes back to MAIN. The reference properties are changed to...

Copy Local = true

Path (read-only property) = C:\Projects\TeamProjectX\Main\Src\ProjectX\Src\Data\BL\bin\Release\test.dll

Everything else is the default.


Why does the path change? How can I have it so that the path doesn't change in the MAIN branch? This is an issue for me because the build will fail. The build is expecting the assembly in the C:\Projects\Framework\Files\Assemblies\Release\ folder not C:\Projects\TeamProjectX\Main\Src\ProjectX\Src\Data\BL\bin\Release\


Please advice, Thanks!

Sep 3, 2011 at 12:10 AM

I think my issue is related and can be resolved by the Bill's blog and this discussion thread.

Sep 6, 2011 at 7:22 PM

I also picked the option #2 "...all branches must be at the same folder depth within the team project..." 

I found option #2 more feasible because you can create a shared folder inside the MAIN at anytime. In other words, option #1 is a subset of option #2 somewhat.

My apologizes for creating multiple discussions based on the same problem. The other discussion is here. I am now clear what needs to be done to fix my issue. BTW, Bill's blog content is not included into the TFS guidelines that is created by VS ALM team.