When I try to run a build through the TFS 2010 build service, I get errors stating that assemblies mentioned in the title can't be found, or rather, it breaks on a using statement for the LongRunningOperationJob in the publishing assembly:

using Microsoft.Office.Server.UserProfiles;

and

using Microsoft.SharePoint.Publishing.Internal;

Also, underneath the errors there is the following warning:

C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1360): The primary reference "Microsoft.SharePoint.Publishing, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c, processorArchitecture=MSIL" could not be resolved because it has an indirect dependency on the framework assembly "System.Web.DataVisualization, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" which could not be resolved in the currently targeted framework. ".NETFramework,Version=v3.5". To resolve this problem, either remove the reference "Microsoft.SharePoint.Publishing, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c, processorArchitecture=MSIL" or retarget your application to a framework version which contains "System.Web.DataVisualization, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35".

The project targets the .Net Framework 3.5 and has the platform target set to "Any CPU". I am using WSPBuilder, the mentioned Assemblies have the copy local flag set to false in the project.

I followed the steps mentioned here:

http://blogs.msdn.com/b/jjameson/archive/2011/02/27/building-sharepoint-2010-solutions-on-a-tfs-2010-build-server.aspx

link|improve this question

feedback

1 Answer

up vote 1 down vote accepted

Had similar issue, and if I recall correctly it was solved by installing ASP.NET and Windows Forms Chart Controls for .NET Framework 3.5 SP1.

link|improve this answer
Yes! that got me further, but now anything related to the SharePoint Client OM starts throwing errors. Will look at the mentioned article again. – Colin Jul 4 '11 at 20:08
The dll it was looking for was related to my custom WCF services and the automatic WCF proxy provided by MS.SharePoint.CLient.ServerRuntime.dll – Colin Jul 4 '11 at 20:31
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.