MSBuild "manual" build does not produce the same output as "Build Solution" through the IDE

Dan,

I will need to post this in multiple entries... looks like the browser/server chokes up on too much data.

Solution file:

Project file:

<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<PropertyGroup>
<Configuration Condition=" '$(Configuration)' == '' ">Debug</Configuration>
<Platform Condition=" '$(Platform)' == '' ">AnyCPU</Platform>
<ProductVersion>8.0.50727</ProductVersion>
<SchemaVersion>2.0</SchemaVersion>
<ProjectGuid>{E40D3A4D-7064-4FAA-BB25-4DBD4E9F4671}</ProjectGuid>
<OutputType>Library</OutputType>
<AppDesignerFolder>Properties</AppDesignerFolder>
<RootNamespace>BusinessObjects.Tests</RootNamespace>
<AssemblyName>BusinessObjects.Tests</AssemblyName>
<AssemblyOriginatorKeyFile>GOV.USDA.NRCS.NASIS.Client.Dev.snk</AssemblyOriginatorKeyFile>
<SignAssembly>true</SignAssembly>
</PropertyGroup>
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
<DebugSymbols>true</DebugSymbols>
<DebugType>full</DebugType>
<Optimize>false</Optimize>
<OutputPath>bin\Debug\</OutputPath>
<DefineConstants>DEBUG;TRACE</DefineConstants>
<ErrorReport>prompt</ErrorReport>
<WarningLevel>4</WarningLevel>
</PropertyGroup>
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' ">
<DebugType>pdbonly</DebugType>
<Optimize>true</Optimize>
<OutputPath>bin\Release\</OutputPath>
<DefineConstants>TRACE</DefineConstants>
<ErrorReport>prompt</ErrorReport>
<WarningLevel>4</WarningLevel>
</PropertyGroup>
<ItemGroup>
<Reference Include="DevExpress.Data.v7.2, Version=7.2.4.0, Culture=neutral, PublicKeyToken=9b171c9fd64da1d1, processorArchitecture=MSIL">
<SpecificVersion>False</SpecificVersion>
<HintPath>..\..\..\external\lib\DevEx\v7.2\DevExpress.Data.v7.2.dll</HintPath>
<Private>True</Private>
</Reference>
<Reference Include="Microsoft.Practices.CompositeUI, Version=1.0.51205.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=MSIL">
<SpecificVersion>False</SpecificVersion>
<HintPath>..\..\..\external\lib\Microsoft.ApplicationBlocks\CAB\Microsoft.Practices.CompositeUI.dll</HintPath>
</Reference>
<Reference Include="nunit.framework, Version=2.4.1.0, Culture=neutral, PublicKeyToken=96d09a1eb7f44a77, processorArchitecture=MSIL">
<SpecificVersion>False</SpecificVersion>
<HintPath>..\..\..\external\lib\NUnit2.4.1\nunit.framework.dll</HintPath>
</Reference>
<Reference Include="System" />
<Reference Include="System.Data" />
<Reference Include="System.Xml" />
</ItemGroup>
<ItemGroup>
<Compile Include="MockObjects\TMBusinessTable.cs" />
<Compile Include="Properties\AssemblyInfo.cs" />
<Compile Include="TBusinessObjectProvider.cs" />
<Compile Include="ValidationTests.cs" />
</ItemGroup>
<ItemGroup>
<ProjectReference Include="..\..\Data Access Layer\CRUD\CRUD.csproj">
<Project>{56EAD126-EE24-4332-9E04-BF474F530278}</Project>
<Name>CRUD</Name>
</ProjectReference>
<ProjectReference Include="..\..\NASIS.Interfaces\NASIS.Interfaces.csproj">
<Project>{2EDC9548-F45D-42A5-897F-081949B53B32}</Project>
<Name>NASIS.Interfaces</Name>
</ProjectReference>
<ProjectReference Include="..\BusinessObjects\BusinessObjects.csproj">
<Project>{5443348C-5B97-4CFF-822B-ECB739D6C6E6}</Project>
<Name>BusinessObjects</Name>
</ProjectReference>
<ProjectReference Include="..\DataDictionary.Tests\DataDictionary.Tests.csproj">
<Project>{2842B313-9C5E-4C55-B957-F6E9986E1C0F}</Project>
<Name>DataDictionary.Tests</Name>
</ProjectReference>
<ProjectReference Include="..\DataDictionary\DataDictionary.csproj">
<Project>{65F5198D-58D5-430A-945E-C46B96B846B6}</Project>
<Name>DataDictionary</Name>
</ProjectReference>
<ProjectReference Include="..\User\User.csproj">
<Project>{B000317D-A389-4254-B5E5-B4655C38890B}</Project>
<Name>User</Name>
</ProjectReference>
</ItemGroup>
<ItemGroup>
<Content Include="..\DataDictionary.Tests\DataDictionaryTestData.xml">
<Link>DataDictionaryTestData.xml</Link>
</Content>
</ItemGroup>
<ItemGroup>
<None Include="App.config" />
<None Include="GOV.USDA.NRCS.NASIS.Client.Dev.snk" />
</ItemGroup>
<Import Project="$(MSBuildBinPath)\Microsoft.CSharp.targets" />
<!-- To modify your build process, add your task inside one of the targets below and uncomment it.
Other similar extension points exist, see Microsoft.Common.targets.
<Target Name="BeforeBuild">
</Target>
<Target Name="AfterBuild">
</Target>
-->
</Project>

Dan,

I'll get you the project files shortly.

But, without even looking at them, I already know that some projects have that particular project reference as "copy local", but most don't have it.

Our phylosophy is that we only set to "copy local" the assemblies that the current project "delivers".

In this case, this is an "interface" project and is used by pretty much all projects, but ends up being "delivered" only by the main project (like framework or .exe).

We also try to have a unit test project for each "regular" project.

For those test projects to execute, they need to have all the necessary assemblies in their output directory. Hence the copy local on those projects of pretty all assemblies except .Net Framework stuff.

As mentioned in my last post, I ran a simple "msbuild" in the same folder using the Orcase March 2007 CTP (using MSBuild 3.5.xxx) and it worked as expected (all references - assemblies and projects - marked "copy local" end up in the output directory for those tests projects).

I guess my next question would be: is there a version of MSBuild between what ships with the latest 2.0 SP and the upcoming 3.5 beta or could we install the 3.5 SDK onto our CI machine to use the latest version of MSBbuild.

Regards,

Eric.

Dan,

The project files should be available at the same location pointed to earlier in the projects.zip file

http://www.sharebig.com/share.php id=s14cfqkejcpcVq4WQ

Thanks again for your help.

We'd like to get to know MSBuild beyond simply building our projects and slowly replace NAnt...

Eric.

Dan,

I will see for reproducing the problem on a smaller project, with little to no code (or no proprietary code).

But at this time, my management does not believe in separate project build process and therefore will not authorize me to continue investigating (this doesn't mean I will do it or that I won't try to reproduce this on my own time ).

Until the standalone installer comes out or we can install the 3.5 build chain, I might try to copy the 3.5 MSBuild binaries or something like that and have it run on our build machine.

It is obviously not an issue for individual developers running VS2k5 on their own machines.

Thanks again for all your help.

If I was to open a customer feedback issue, where would I go

Regards,

Eric.