Share →

This is SSW’s first time using Team Build 2010 to automatically create a Silverlight application. In the past the guys have used Cruse Control, but we want to move to a pure TFS 2010 solution. When one of our developers (Allan) added a Silverlight 3 project to the Solution our build server spat it out.

clip_image001
Figure: Build SSW.SqlDeploy_20100303.8 failed when trying to build a Silverlight application.

Usually the person who broke the build should now be the one responsible for babysitting it until the next person breaks the build. In this case we had not agreed that as part of our project prep so I think I will need to wait until the retrospective at the end of our current, and first for this project, sprint.

Problem 1: First time for Silverlight compile on the Build Server.

Because Allan added the first Silverlight 3 application to the Solution the build server hiccupped as only the Silverlight 2 SDK was installed on it and it was a Silverlight 3 project. I have highlighted below where the problem was located.

 image
Figure: The Silverlight targets file was not found on the build server.

I downloaded and installed the Silverlight 3 SDK from Microsoft, and hoped all would be well.

But the build failed again…

clip_image003
Figure: SSW.SqlDeploy_20100303.10 failed still trying to find targets.

Problem 2: This was due to the web targets not being installed.

At this point I got fed up and copied the contents of my local directory “C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0” to the same folder on the build server.

image
Figure: MSBuild could not find the web targets.

But the build failed again…

image
Figure: SSW.SqlDeploy_20100303.11 failed again trying to build Silverlight.

Problem 3: Can’t build Silverlight 3 projects with MSBuild 64-bit (the default)

There is a nasty bug in the Silverlight SDK that means that you can’t build using the MSBuild 64-bit process. But on a 64-bit OS, the 64-bit MSBuild is used by default… so how to change it.

image
Figure: Why is it saying that the SDK is not installed… oh, a bug.

This is an easy fix, but a hard to find solution. if you Open up your “build process definition” and expand the Advanced tree you will see that there is a MSBuild Platform option that is set to “Auto”, change this to “X86”.

clip_image005
Figure: You MUST set the MSBuild Platform to X86 to build a Silverlight project,

And the build failed again…

image
Figure: SSW.SqlDeploy_20100304.04 failed again trying to do code analysis.
Note: This was only run 20 or so minutes after the last build, but my build server happens to be in Australia :)

Problem 4: Can’t run Code Analysis on Build Server

Now I get Code Analysis errors…

image
Figure: Why would I be getting code analysis errors? Could it be that it is not installed?

To fix this one I just bit the bullet and installed Visual Studio 2010 onto the Build server, and…

clip_image007
Figure: Successful builds give me a warm fuzzy feeling…

Conclusion

The things that should be installed on the build server are:

  • Team Foundation Build Services 2010 or 2008 or 2005
  • Visual Studio 2010/2008/2005
  • Add-on’s for TFS or Visual Studio that may be required to execute the build.

The options you should set for any Build that has 32-bit dependencies that are causing a problem:

  • You MUST set the MSBuild Platform to X86 to build a project that can’t be built in 64-bit MSBuild.

 

 

 

 

 

 

 

 


Need Help?

www.SSW.com.au

SSW was the first company in the world outside of Microsoft to deploy Visual Studio 2010 Team Foundation Server to production, not once, but twice.

Team Foundation Server

Visual Studi2010 ALM SSW provides expert Visual Studio ALM guidance including installation, configuration and customisation through our four Microsoft Visual Studio ALM MVP’s in three countries; Australia, Beijing and the UK. They have experience deploying to small development shops all the way through to large blue chips.

Professional Scrum Developer Training

Professional Scrum Developer Training SSW has six Professional Scrum Developer Trainers who specialise in training your developers in implementing Scrum with Microsoft’s Visual Studio ALM tools.

  • Simon Hart

    Thanks. This is really useful post.

    I noticed you mentioned some SCRUM terminalogy. Do you know of any SCRUM project templates that integrate into TFS 2010 as I can’t seem to find any.

    Cheers
    Simon

  • Martin Hinshelwood

    The default template “MSF Agile” can be, and is used for Scrum. That is what we use and teach with the RC. There is also a beta of the Scrum for Team System 3.0 template from EMC (was conchango).

    There will be more information on other options around the launch and a new Certified Template proggram comming.

  • Peter Gfader

    I don’t want to install VS2010 on my build server just to fix
    “MSBuild could not locate the Code Analysis tool at”

    Any hints?

  • Martin Hinshelwood

    Is their any reason why not? If all you dev’s are licenced then you do not need an extra licence for your build server!

  • Peter Gfader

    I want my servers nice and clean, and avoid cluttering up with “crap” ;-)

    BTW
    I got it working without installing VS2010
    Setting the registry key
    HKEY_LOCAL_MACHINE\Software\Microsoft\VisualStudio\10.0\Setup\EDev@FxCopDir
    to the path where Code Analysis is installed

  • Latest News

    you are right. Even I got it done without the installation of VS2010