How to Build Multiple Dependent .NET Solutions in TeamCity?

We've got an application which components are developed in multiple Visual Studio solutions (.sln). From time to time a solution is added or removed. The build output such as DLLs are copied into a shared folder. Projects from other solutions reference those DLLs. Here's a simplified example: solutions A and B consist of two projects each. The project B2 of solution B references project A2 of solution A.

teamcity-multiplesolutions.png

Side note: We're in the process to replace the shared drive with NuGet packages; however, the following question is still apparent.

We'd like TeamCity to automatically(!!) resolve dependencies between projects. So in the above example we'd like that TeamCity builds solution A first and solution B next. How can we configure TeamCity to pick up these dependencies automatically without maintaining them manually?

What is the easiest way to achieve this?

3 comments
Comment actions Permalink

Please describe how exactly do you plan to achive your goal via nuget packages?

0
Comment actions Permalink

Hi Evgeniy, the NuGet package structure has no relevance to the question. I was only mentioning it to avoid answers that refer to "use NuGet". We are still a year away or so to get NuGet into place fully. We need a solution that addresses the problem as described; excluding NuGet.

0
Comment actions Permalink

Ok. In my point of view it is not a TeamCity-specific issue since i expect that you should be able to reproduce such a build procedure locally on dev machines.
As far as i know .net ecosystem itself doesn't provide the solution. Dependency management in .net just doesn't work in this way.
There are always an options to write your own plugin for msbuild or generate solutions (.sln files) automatically. But the complexity of these workarounds is pretty high and these solutions are not straightforward and maintainable at all.

0

Please sign in to leave a comment.