New Post: BTDF Build/Deploy: EXEC : error : Failed to add resource(s).

No…I checked your previous responses where you diagnosed specification of the same DLL in different item groups in Deployment.btdproj. Nothing like that here:

Here is Deployment.btdproj:

<?xmlversion="1.0"encoding="utf-8"?>

<!--

Deployment Framework for BizTalk 5.0

Copyright (C) 2004-2012 Thomas F. Abraham and Scott Colestock

-->

<Projectxmlns="http://schemas.microsoft.com/developer/msbuild/2003"DefaultTargets="Installer"ToolsVersion="4.0">

<PropertyGroup>

<ConfigurationCondition="'$(Configuration)' == ''">Release</Configuration>

<PlatformCondition="'$(Platform)' == ''">x86</Platform>

<SchemaVersion>1.0</SchemaVersion>

<ProjectName>Aoc.Dx.Get.Services</ProjectName>

<ProjectVersion>1.0</ProjectVersion>

<IncludeOrchestrations>True</IncludeOrchestrations>

<IncludeTransforms>True</IncludeTransforms>

<IncludeDeploymentTest>True</IncludeDeploymentTest>

<SkipIISReset>True</SkipIISReset>

<IncludeSSO>False</IncludeSSO>

<UsingMasterBindings>True</UsingMasterBindings>

<RequireXmlPreprocessDirectives>False</RequireXmlPreprocessDirectives>

</PropertyGroup>

<PropertyGroup>

<!-- Properties related to building an MSI for server deployments-->

<!-- BizTalk App Version Upgrade-->

<!-- For each new product release to be deployed to your BizTalk servers:-->

<!-- 1) Increment ProductVersion-->

<!-- 2) Generate a new GUID and update ProductId with the new GUID-->

<!-- This allows the new MSI to automatically uninstall (not undeploy!) the old MSI and install the new one. -->

<ProductVersion>1.0.4</ProductVersion>

<ProductId>c4734394-ff5d-41c1-96cf-aa46ee8d9f68</ProductId>

<!-- BizTalk App Version Upgrade-->

<ProductName>Aoc.Dx.Get.Services for BizTalk</ProductName>

<Manufacturer>AOC</Manufacturer>

<PackageDescription>Aoc.Dx.Get.Services</PackageDescription>

<PackageComments>Aoc.Dx.Get.Services</PackageComments>

<!-- NEVER change the ProductUpgradeCode.-->

<ProductUpgradeCode>92cf86fc-5717-4574-82dc-b16e44a15d84</ProductUpgradeCode>

</PropertyGroup>

<!-- Under TFS Team Build, set CustomizableOutDir property to true in TFS 2005/2008/2010 UpgradeTemplate.-->

<!-- With a workflow build, copy the default template then modify the MSBuild task for the solution build. Set OutDir to blank and -->

<!-- CommandLineArguments to String.Format("/p:SkipInvalidConfigurations=true;TeamBuildOutDir=""{0}"" {1}", BinariesDirectory, MSBuildArguments). -->

<PropertyGroupCondition="'$(Configuration)' == 'Debug'">

<DeploymentFrameworkTargetsPath>$(MSBuildExtensionsPath)\DeploymentFrameworkForBizTalk\5.0\</DeploymentFrameworkTargetsPath>

<OutputPathCondition="'$(TeamBuildOutDir)' == ''">bin\Debug\</OutputPath>

<OutputPathCondition="'$(TeamBuildOutDir)' != ''">$(TeamBuildOutDir)</OutputPath>

<DeployPDBsToGac>false</DeployPDBsToGac>

</PropertyGroup>

<PropertyGroupCondition="'$(Configuration)' == 'Release'">

<DeploymentFrameworkTargetsPath>$(MSBuildExtensionsPath)\DeploymentFrameworkForBizTalk\5.0\</DeploymentFrameworkTargetsPath>

<OutputPathCondition="'$(TeamBuildOutDir)' == ''">bin\Release\</OutputPath>

<OutputPathCondition="'$(TeamBuildOutDir)' != ''">$(TeamBuildOutDir)</OutputPath>

<DeployPDBsToGac>false</DeployPDBsToGac>

</PropertyGroup>

<PropertyGroupCondition="'$(Configuration)' == 'Server'">

<DeploymentFrameworkTargetsPath>Framework\</DeploymentFrameworkTargetsPath>

<!-- Get our PDBs into the GAC so we get file/line number information in stack traces.-->

<DeployPDBsToGac>true</DeployPDBsToGac>

</PropertyGroup>

<!--ItemGroup>

<PropsFromEnvSettings Include="SsoAppUserGroup;SsoAppAdminGroup" />

</ItemGroup-->

<ItemGroupCondition="'$(Configuration)' == 'Debug'">

<!-- We name our host(s) explicitly to avoid having the framework bounce them all.-->

<BizTalkHostsInclude="BizTalkServerApplication" />

</ItemGroup>

<ItemGroupCondition="'$(Configuration)' == 'Release'">

<!-- We name our host(s) explicitly to avoid having the framework bounce them all.-->

<BizTalkHostsInclude="BizTalkServerApplication" />

</ItemGroup>

<ItemGroupCondition="'$(Configuration)' == 'Server'">

<!-- We name our host(s) explicitly to avoid having the framework bounce them all.-->

<BizTalkHostsInclude="BizTalkServerApplication" />

</ItemGroup>

<!-- !!! TODO !!!-->

<!-- Add ItemGroup elements that contain one or more Schemas, Orchestrations, Transforms, etc. elements that describe -->

<!-- the specific artifacts in your solution that need to be deployed. Use IntelliSense as a guide. -->

<ItemGroup>

<SchemasInclude="Aoc.Dx.Get.Services.SCHEMAS.dll">

<LocationPath>..\SCHEMAS\bin\$(Configuration)</LocationPath>

</Schemas>

</ItemGroup>

<ItemGroup>

<TransformsInclude="Aoc.Dx.Get.Services.MAPS.dll">

<LocationPath>..\MAPS\bin\$(Configuration)</LocationPath>

</Transforms>

</ItemGroup>

<ItemGroup>

<OrchestrationsInclude="Aoc.Dx.Get.Services.ORCHESTRATIONS.dll">

<LocationPath>..\ORCHESTRATIONS\bin\$(Configuration)</LocationPath>

</Orchestrations>

</ItemGroup>

<ItemGroup>

<DeploymentTestInclude="DeploymentVerification.Tests.dll">

<LocationPath>..\DeploymentVerification.Tests\bin\$(Configuration)</LocationPath>

</DeploymentTest>

</ItemGroup>

<!-- The app.config file is set in VS to "Copy always" to the output directory, and here it is included in the MSI. Below it gets preprocessed to merge-in the environment-specific settings for the deployment verification tests.-->

<ItemGroup>

<AdditionalFilesInclude="app.config">

<LocationPath>..\DeploymentVerification.Tests\bin\$(Configuration)</LocationPath>

</AdditionalFiles>

</ItemGroup>

<ItemGroup>

<FilesToXmlPreprocessInclude="app.config">

<LocationPath>..\DeploymentVerification.Tests\bin\$(Configuration)</LocationPath>

<OutputFilename>DeploymentVerification.Tests.dll.config</OutputFilename>

</FilesToXmlPreprocess>

</ItemGroup>

<!-- !!! TODO !!!-->

<ImportProject="$(DeploymentFrameworkTargetsPath)BizTalkDeploymentFramework.targets" />

<!--

The Deployment Framework automatically packages most files into the server install MSI.

However, if there are special folders that you need to include in the MSI, you can

copy them to the folder $(RedistDir) in the CustomRedist target.

To include individual files, add an ItemGroup with AdditionalFiles elements.

-->

<TargetName="CustomRedist">

</Target>

<TargetName="CustomFinalDeploy"Condition="'$(Configuration)' == 'Server'">

<DeleteFiles="$(PortBindings)"TreatErrorsAsWarnings="false" />

</Target>

</Project>