I have a situation where we have a CSLA Silverlight solution that is built using the Microsoft TFS Build. The problem is we added a project to the solution that requires the .NET version of the business object assembly and because the TFS build process places the output into a single release folder, the new project ends up attempting to build against the Silverlight version of the assembly instead of the .NET version.
Bottom line, My question is are the Silverlight and .NET versions of a business object assembly required to have the same output file name?
As you have seen TeamBuild and VisualStudio IDE buld do not do the the exact same thing. What you need to do is edit the project definitions for both the client and server business dlls to change the output path to put the files in subfolders when building inside of TeamBuild. Here is an example:
<OutDir Condition=" '$(TeamBuildOutDir)'=='' And '$(BuildingInsideVisualStudio)' != 'true' ">..\Output\Alcatraz.Business.Client\</OutDir>
<OutDir Condition=" '$(TeamBuildOutDir)'!='' ">$(TeamBuildOutDir)Alcatraz.Business.Client</OutDir>
Copyright (c) Marimer LLC