Visual Studio 2010 and TFS Link Paths

Question

I have a project in which I use reference paths to store the necessary DLLs.
My problem is that when I checked them on my TFS server and after my colleague got the latest version from the TFS server, he could not see the link paths on the properties page in the project files.

What have I done wrong?

Answer 1

Building reference paths is not part of the project file. Visual Studio saves them in Customizing file (* .csproj.user or * .vbproj.user), which should not be added to the original control .

If you want to share assembly reference targets with the rest of the team , you can manually add them to the project file with the <AssemblySearchPaths> element:

 <PropertyGroup> <AssemblySearchPaths> ..\..\MyReferences\; </AssemblySearchPaths> </PropertyGroup> 

Answer 2

The source paths are stored in a * .csproj.user file, which is a user file containing project parameters. In order for your colleague to create a project after receiving the last of the initial control, he needs to manually add a reference path to the project itself.

Answer 3

I found a better working solutin for me, adding <Target> with the name BeforeResolveReferences , which sets the AssemblySearchPaths property, adding my CommonLibs folder as the first path to search for assemblies:

 <Target Name="BeforeResolveReferences"> <CreateProperty Value="..\CommonLibs\;$(AssemblySearchPaths)"> <Output TaskParameter="Value" PropertyName="AssemblySearchPaths" /> </CreateProperty> </Target> 

The assemblies included in the assembly kit are all located in the folder named "CommonLibs" at the same level as the solution folder.

Adding <AssemblySearchPaths> , as mentioned in the previous answer, unfortunately does not work for me:

Although the DLLs referenced by the new path can be found by the compiler, regular System.* Assemblies can no longer be found.

In Visual Studio 2010, the <AssemblySearchPaths> files in the project files may be invalid because the editor warns that this element is invalid.