Team City build of orchard CMS failing

Question

I am new to Orchard and MVC 3. Now, am trying to build my solution under Team City. But it is not building successfully.

I had downloaded the whole source from orchard's website. The directory structure is

OrchardSite (Root Folder) ->Lib (Root's Sub Folder) ->Src (Root's Sub Folder)

Both these folders are a part of my repo.

The build in Team City fails and complains of not being able to find any dependencies. A snapshot of the error log :

[12:09:09]: Orchard\Orchard.Framework.csproj (13s)
[12:09:10]: [Orchard\Orchard.Framework.csproj] CoreCompile (12s)
[12:09:10]: [CoreCompile] Csc (12s)
[12:09:21]: [Csc] ContentManagement\ContentItemBehavior.cs(2, 7): error CS0246: The type or namespace name 'ClaySharp' could not be found (are you missing a using directive or an assembly reference?)
[12:09:21]: [Csc] ContentManagement\ContentItemBehavior.cs(5, 40): error CS0246: The type or namespace name 'ClayBehavior' could not be found (are you missing a using directive or an assembly reference?)
[12:09:21]: [Csc] ContentManagement\DefaultContentDisplay.cs(5, 7): error CS0246: The type or namespace name 'ClaySharp' could not be found (are you missing a using directive or an assembly reference?)
[12:09:21]: [Csc] ContentManagement\IContentBehavior.cs(1, 7): error CS0246: The type or namespace name 'ClaySharp' could not be found (are you missing a using directive or an assembly reference?)

Not sure what needs to be done. Can someone please help me out?

P.S. I don't want to make this post too long - so, if there is anything that you need to know and I have missed out, please let me know. Thanks!

Answer 1

We use Team City as our continuous integration. You can probably take a peek at our configuration: http://teamcity.codebetter.com/project.html?projectId=project143&tab=projectOverview

Here is a copy of our settings:

General Settings Name: * Description:
Build number format: *
Format may include '{0}' as a placeholder for build counter value, for example 1.{0}. It may also contain a reference to any available parameter, for example, VCS revision number: %build.vcs.number.*%. Note: maximum length of a build number after all substitutions is 256 characters.

Build counter: * Reset counter Artifact paths:
Edit artifact paths:

Hide New line or comma separated paths to build artifacts. Support ant-style wildcards like dir/*/.zip and target directories like *.zip => winFiles,unix/distro.tgz => linuxFiles, where winFiles and linuxFiles are target directories. Fail build if:
build process exit code is not zero at least one test failed an error message is logged by build runner it runs longer than minutes an out of memory or crash is detected (Java only) Build options: enable hanging builds detection enable status widget
Limit the number of simultaneously running builds (0 - unlimited)

Checkout Settings VCS checkout mode:
Checkout directory:
Leave blank to use default checkout directory on an agent.

Clean all files before build:
VCS Labeling VCS labeling mode: Do not label Successful only Always Labeling pattern:
Choose VCS roots to label: Orchard Mercurial (CodePlex) (1.x)

Build Step Runner type:
Runner for MSBuild files Step name:
You can specify build step name to distinguish it from other steps. Build file path: *
Specified path should be relative to the checkout directory.

Working directory:
Optional, specify if differs from the checkout directory.

MSBuild version:
MSBuild ToolsVersion:
Run platform:
Targets:
Enter targets separated by space or semicolon.

Command line parameters:
Enter additional command line parameters to MSBuild.exe.

Reduce test failure feedback time: Run recently failed tests first .NET Coverage .NET Coverage tool:

Build Trigger Parameters Description VCS Trigger Quiet period: 300 seconds (default)