You don't want to nest the calls, try this: Target Name="Build.
You don't want to nest the calls, try this: The items within a target are executed in sequence.
Well, that was embarrasingly simple. Thank you! :) – Rune Jacobsen Nov 9 at 5:48 No worries, as an aside, I'd probably split test from build and give yourself a test target and a build target (although the example bit of msbuild I checked doesn't!), then you have options to run whichever targets in whichever context you want.
– Murph Nov 9 at 9:01 Thanks, yeah, I'll probably go in that direction. Perhaps it will make it easier to get code coverage going in TeamCity as well. :) – Rune Jacobsen Nov 9 at 19:14 I intend to end up with targets for (something like) build, unit test, package, deploy, smoke test - currently I have the last 3 wrapped into a single target (it works...).
I also need an integration test target. Challenge is I have a lot of projects to wrap all of this stuff into – Murph Nov 9 at 9:37.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.