You do this by creating 'Artifacts and artifact dependencies.
If project A depends on project B, then you create an Artifact in project B using the artifact path, for example:
bin/Release/B.dll
Then in project A, you establish the dependency of the artifact with B using the path, for example:
B.dll
And set the destination path, wherever Project A expects to find B.dll, for example.
./Libs
You can do other interesting things, such as automatically archiving all your artifacts in zip using the syntax:
bin/Release/*.dll => B.zip
and access them through:
B.zip!B.dll
All these paths belong to the assembly directories, therefore they are simplified, and you do not need to worry about the folders of the TeamCity manual or use absolute paths.
source share