Reputation: 1370
Ok so I have to admit, I'm very new to all of this build automation stuff. But basically what I'm wondering is if there is a way to wire up my build definitions in such a way that if I have a case like so
then when I make changes to ProjectA and check them in, the build process would automatically also build ProjectB, and finally ProjectC, and report any errors.
So is there a way to accomplish this, or should this type of thing be handled somehow completely differently in the first place?
Upvotes: 2
Views: 3065
Reputation: 14164
The process you are referring to is the crux of the practice known as Continuous Integration.
TFS does it very well: simply set your build definition Trigger
to Continuous Integration
and set the Workspace
working folder to the parent folder of the three projects. This way, any change in one of the projects will trigger a build.
MSDN: Build and Deploy Continuously
Upvotes: 5
Reputation: 526
You can use a visual studio solution and use project references between the projects. Then build the solution on your build server.
Upvotes: 0