SharePoint project doesn't build on cc.net, but does build on developer workstations

Question

I can build my code locally and on another developer's machine, but cc.net fails to build the project when I check in the code.

I know that I experience a similar issue when I switch between .NET Framework 4 and .NET Framework 4 Client Profile on a console application. .NET Framework 4 is desired for Sharepoint integration, but I've checked the Project settings, and it appears configured to .NET Framework 4. So now I'm at a bit of a loss as to what step to take next.

Here is the line of code that cannot be resolved:

using Microsoft.SharePoint.Client;

Here is cc.net's output

Errors (1):

Repository.cs (15,17): error

CS0234: The type or namespace name 'SharePoint' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?)


Warnings (4)

c:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (1360,9): warning MSB3245: Could not resolve this reference. Could not locate the assembly "Microsoft.SharePoint.Client". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.

c:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets (1360,9): warning MSB3245: Could not resolve this reference. Could not locate the assembly "Microsoft.SharePoint.Client.Runtime". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.

Answer 1

You simply need the SharePoint DLLs available to the compiler. The simplest way is to install SharePoint but you can also put the DLLs in the build path or modify the build configuration to pick up the DLLs from a specified folder.

Answer 2

I think the issue is that the SharePoint client object model does not support .net 4.0 framework per this article. http://msdn.microsoft.com/en-us/library/ee857094.aspx

Change your target framework to 3.5 and retry, although it is strange that it works on your machine?????

As far as needing to install SharePoint that would only be true if you where using the Server Object model but it appears you are using the client object model so you should be fine.

Answer 3

You need SharePoint installed on your build server to make this work, or alternatively to copy SharePoint DLLs to the production server. There is no guide to direct you on how to configure CruiseControl to build SharePoint projects but this guide for TFS 2010 should help you to configure your environment for building SharePoint projects.