Build order not being observed

The issue it seems is arrising from TeamCity not following 'an element' of the project build order for a solution...

There are around 15 projects in the solution and most projects have dependencies which are observed by TeamCity...

However in this case one build order was not observed, so the dll was not compiled, and TeamCity said, "No, the computer says, No!", i.e. assembly reference failure.

Is there a logical reason for this as opposed to an aberation?

P.S. The solution builds without issue in Visual Studio 2010 (VS2010) from a freshly checked out SVN version, and upon inspection the build order for VS2010  is correct.

P.P.S. Is it because TeamCity looks for project dependencies and not build order?

For some background to this issue please look at
http://devnet.jetbrains.com/message/5520563#5520563

4 comments
Comment actions Permalink

Hi,

When build starts it calls another process (MSBuild), so TeamCity does not resolve any dependencies itself. TeamCity uses MSBuild, and its behavior differs form Visual Studio IDE (devenv.exe) (later then 2013 version).
Can you please try to run build via console in TeamCity agent working directory using msbuild.exe (you can look up the command line used by TeamCity in the build log)? Does it execute successfully?

0
Comment actions Permalink

Hi,

thanks for the reply... interesting.... i'll give it a go later... but do you know if TeamCity then uses a default build using something like MSBUILD SOLUTIONFILE.SLN ?

Is there an option to create my own MSBUILD in the form of say a batch file, that TeamCity would use?

0
Comment actions Permalink

In TeamCity you can configure Command line runner, which can run any script supported by OS.

0
Comment actions Permalink

ok thats great, thanks for all your help!


0

Please sign in to leave a comment.