This Question is Possibly Answered

1 "correct" answer available (4 pts) 2 "helpful" answers available (2 pts)
1 Replies Last post: Oct 17, 2011 2:57 PM by Michael Kuzmin  
Daren Willman Newbie 1 posts since
Oct 13, 2011
Currently Being Moderated

Oct 13, 2011 11:53 PM

Two TFS Collections Issue

Hi,

 

On my TFS server I have alot of seperate project collections setup but they all depend on one particular project collection (basically a set of class libraries used in all our applications).  I was able to setup a build configuration on the class libraries no problem since it doesn't depend on anything else.  However, when I try to create a project for an actual application that uses the libraries it cannot find them because they aren't a part of that particular TFS project. 

 

Is there anyway I can include these references into a TeamCity build?

 

This is the compile error I get in TeamCity: The project file "C:\TeamCity\buildAgent\work\CCHv2\CCHv2\..\Csla-3.8.1\Csla-3.8.1.csproj" was not found.

 

My sln file for the application is looking for a relative directory on my file system for the libraries since its setup that way on my development box...  Not sure there is an easy answer short of redoing my TFS to one big collection...  Any ideas?

 

Thanks for the help!

Michael Kuzmin JetBrains 1,451 posts since
Jul 30, 2005
Currently Being Moderated
Oct 17, 2011 2:57 PM in response to: Daren Willman
Re: Two TFS Collections Issue

Hi Daren

 

There are two options:

  1. If you want to build all the sources together all the time,a тв just have a copy of the library in all the projects, then attach two VCS roots to your build configuration and set checkout rules to redirect files to subfolders.
  2. If the library should be compiled and published separatelly, then set artifact dependency to obtain the binaries, and use MSBuild runned instead of Visual Studio SLN runner to build specific projects within a solution.

 

Michael

More Like This

  • Retrieving data ...