May
20
2008
If you want to integrate Silverlight 2.0 Beta 1 in your Continuous Integration system, in my case Team City), it is better to read the readme of Silverlight 2.0 Beta 1 SDK here.
The important part in our case is the following one:
Using MSbuild to build a solution in a command line doesn’t copy the Silverlight project output to the linked web project
We don’t have complete support for command line msbuild usage to build solutions with Silverlight projects which also includes 64 bits MSBuild support.
So basically I made a copy manually from the source of the Silverlight project to the output path of my MSBuild project:
<!--HACK Fix the missing copy of ClientBin -->
<!--http://www.microsoft.com/silverlight/resources/readme.aspx?v=2.0&sdk=true -->
<!--Using MSbuild to build a solution in a command line doesn’t copy the Silverlight project output to the linked web project
We don’t have complete support for command line msbuild usage to build solutions with Silverlight projects which also includes 64 bits MSBuild support.
-->
<Message Condition=" '$(Configuration)|$(Platform)' == 'Staging|AnyCPU' " Text="### HACK Silverlight MSBUILD ###" />
<MakeDir Condition=" '$(Configuration)|$(Platform)' == 'Staging|AnyCPU' " Directories="$(OutputPath)\ClientBin" ContinueOnError="true" />
<Copy Condition=" '$(Configuration)|$(Platform)' == 'Staging|AnyCPU' " SourceFiles="$(MSBuildProjectDirectory)\..\..\Sources\VideoPlayer\ClientBin\VideoPlayer.xap" DestinationFiles="$(OutputPath)\ClientBin\VideoPlayer.xap" />
<!--EndHACK -->
Now my web application is compiled, deployed and works!