Simple Question Deploying and Biztalk Application Name

Topics: Server Deployment
Jun 11, 2015 at 9:43 PM
Hi
I am new to BTDF. I am learning with a small biztalk solution that I previously deployed manually. The solution name = dpBiztalkSolution and holds 2 projects.
The first project is named dpBiztalkSolution (same as the solution). It contains a schema and an Orch.
The second project is C# project named Manager and it has a .Net component.

Originally, the solution was manually deployed from Visual Studio to a Biztalk Application called dpBizSol. This was configured on the Properties Deployment tab in Visual Studio under Application Name = dpBizSol.

I followed the help on http://www.tfabraham.com/BTDFDocs/V5_5/ in order to try and automate the deployment.

After exporting the bindings of the working dpBizSol biztalk application to PortBindingsMaster.xml in the BTDF folder, I built the solution and tried to do an Undeploy. But from the Output window in VS, it says: "Did not find Biztalk Application 'dpBiztalkSolution'".

So, basically I am having trouble instructing BTDF to look for a Biztalk application named "dpBizSol" instead of "dpBiztalkSolution".

Thanks in advance!
Jun 12, 2015 at 6:07 PM
Hi Tica,

It seems there is a problem in btdf file can you please share btdf project code.

Thanks,
Sharad
Jun 12, 2015 at 7:48 PM
Thank you Sharad!

This is the Deployment.btdfproj file

<?xml version="1.0" encoding="utf-8"?>
<!-- Deployment Framework for BizTalk 5.0 Copyright (C) 2004-2012 Thomas F. Abraham and Scott Colestock --> <Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003" DefaultTargets="Installer" ToolsVersion="4.0">
<PropertyGroup>
<Configuration Condition="'$(Configuration)' == ''">Debug</Configuration>
<Platform Condition="'$(Platform)' == ''">x86</Platform>
<SchemaVersion>1.0</SchemaVersion>
<ProjectName>dpBiztalkSolution</ProjectName>
<ProjectVersion>1.0</ProjectVersion>
<IncludeSchemas>True</IncludeSchemas>
<IncludeOrchestrations>False</IncludeOrchestrations>
<IncludeTransforms>False</IncludeTransforms>
<IncludePipelines>False</IncludePipelines>
<IncludeComponents>False</IncludeComponents>
<IncludePipelineComponents>False</IncludePipelineComponents>
<IncludeCustomFunctoids>False</IncludeCustomFunctoids>
<IncludeVocabAndRules>False</IncludeVocabAndRules>
<IncludeVirtualDirectories>False</IncludeVirtualDirectories>
<IncludeMessagingBindings>True</IncludeMessagingBindings>
<IncludeDeploymentTest>False</IncludeDeploymentTest>
<Includelog4net>False</Includelog4net>
<IncludeSSO>False</IncludeSSO>
<IncludeEsbItineraries>False</IncludeEsbItineraries>
<IncludeBam>False</IncludeBam>
<IncludeInstallUtilForComponents>False</IncludeInstallUtilForComponents>
<UsingMasterBindings>True</UsingMasterBindings>
<RequireXmlPreprocessDirectives>False</RequireXmlPreprocessDirectives>
<ApplyXmlEscape>False</ApplyXmlEscape>
<IncludeSettingsSpreadsheetInMsi>True</IncludeSettingsSpreadsheetInMsi>
<IncludeCompsAndVDirsAsResources>False</IncludeCompsAndVDirsAsResources>
<SkipIISReset>True</SkipIISReset>
<SkipHostInstancesRestart>False</SkipHostInstancesRestart>
<StartApplicationOnDeploy>True</StartApplicationOnDeploy>
<EnableAllReceiveLocationsOnDeploy>True</EnableAllReceiveLocationsOnDeploy>
<StartReferencedApplicationsOnDeploy>True</StartReferencedApplicationsOnDeploy>
<UseIsolatedAppDomain>False</UseIsolatedAppDomain>
<EnableBizTalkExtendedLogging>False</EnableBizTalkExtendedLogging>
<EnableBizTalkAssemblyValidation>False</EnableBizTalkAssemblyValidation>
<EnableBizTalkCorrelationValidation>False</EnableBizTalkCorrelationValidation>
<EnableBizTalkSchemaValidation>False</EnableBizTalkSchemaValidation>
</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.0</ProductVersion>
<ProductId>b758eda5-47cc-4147-a7b2-9c77fa999200</ProductId>
<!-- BizTalk App Version Upgrade -->
<ProductName>dpBiztalkSolution for BizTalk</ProductName>
<Manufacturer>Deployment Framework User</Manufacturer>
<PackageDescription>dpBiztalkSolution</PackageDescription>
<PackageComments>dpBiztalkSolution</PackageComments>
<!-- NEVER change the ProductUpgradeCode. -->
<ProductUpgradeCode>cb23754b-c53b-4ce7-b62d-20927d315160</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). --> <PropertyGroup Condition="'$(Configuration)' == 'Debug'">
<DeploymentFrameworkTargetsPath>$(MSBuildExtensionsPath)\DeploymentFrameworkForBizTalk\5.0\</DeploymentFrameworkTargetsPath>
<OutputPath Condition="'$(TeamBuildOutDir)' == ''">bin\Debug\</OutputPath>
<OutputPath Condition="'$(TeamBuildOutDir)' != ''">$(TeamBuildOutDir)</OutputPath>
<DeployPDBsToGac>false</DeployPDBsToGac>
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)' == 'Release'">
<DeploymentFrameworkTargetsPath>$(MSBuildExtensionsPath)\DeploymentFrameworkForBizTalk\5.0\</DeploymentFrameworkTargetsPath>
<OutputPath Condition="'$(TeamBuildOutDir)' == ''">bin\Release\</OutputPath>
<OutputPath Condition="'$(TeamBuildOutDir)' != ''">$(TeamBuildOutDir)</OutputPath>
<DeployPDBsToGac>false</DeployPDBsToGac>
</PropertyGroup>
<PropertyGroup Condition="'$(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>
<!-- !!! 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>
<Schemas Include="dpBiztalkSolution.dll">
  <LocationPath>..\dpBiztalkSolution\bin\$(Configuration)</LocationPath>
</Schemas>
</ItemGroup>
<ItemGroup>
    <Schemas Include="Manager.dll">
        <LocationPath>..\Manager\bin\$(Configuration)</LocationPath>
    </Schemas>
</ItemGroup>
<!-- !!! TODO !!! -->
<Import Project="$(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. --> <Target Name="CustomRedist">
</Target>
</Project>
Jun 13, 2015 at 5:21 AM
Hi Tica,

1) Can you try changing your project name as "dpBizSol" as you want your BizTalk application name like this.

<PropertyGroup>
<Configuration Condition="'$(Configuration)' == ''">Debug</Configuration>
<Platform Condition="'$(Platform)' == ''">x86</Platform>
<SchemaVersion>1.0</SchemaVersion>
<ProjectName>dpBizSol</ProjectName>
<ProjectVersion>1.0</ProjectVersion>
<IncludeTransforms>False</IncludeTransforms>
<IncludeComponents>True</IncludeComponents>
<IncludeSchemas>true</IncludeSchemas>
<IncludeOrchestrations>false</IncludeOrchestrations>
<IncludeMessagingBindings>False</IncludeMessagingBindings>
<UsingMasterBindings>True</UsingMasterBindings>
<RequireXmlPreprocessDirectives>False</RequireXmlPreprocessDirectives>
<ApplyXmlEscape>True</ApplyXmlEscape>
<IncludeSettingsSpreadsheetInMsi>False</IncludeSettingsSpreadsheetInMsi>
<EnableAllReceiveLocationsOnDeploy>False</EnableAllReceiveLocationsOnDeploy>
</PropertyGroup>

2) Since your manager project is a .net component project so you cant give it as schema please change that one also to;

<ItemGroup>
<Components Include="Manager.dll">
  <LocationPath>..\Manager\bin\$(Configuration)</LocationPath>
</Components>
</ItemGroup>

please try this hope this solves your problem.

Thanks,
Sharad
Coordinator
Jun 13, 2015 at 5:52 AM
Sharad is correct that the property ProjectName is commonly used for the BizTalk application name. You can also explicitly set a property named BizTalkAppName, but that is typically not necessary.

Thanks,
Tom