Thanks for response,
__
Is this a brand new BizTalk solution and projects created with BizTalk 2013, and a new Deployment Framework project created with the Add New Project wizard?__
as per your comments,
it is biztalk2013 sloution project, added the new Deployment Framework project to the project.
There is no settings file specified (/s:""").
_means?
i added setting file also._
This is my btdf file:
<?xml version="1.0" encoding="utf-8"?>
<!-- Deployment Framework for BizTalk 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>
<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'">
<PropertyGroup Condition="'$(Configuration)' == 'Release'">
<PropertyGroup Condition="'$(Configuration)' == 'Server'">
<!--<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>
<!--<ItemGroup><Orchestrations Include="BizTalk Server Project2.dll"><LocationPath>C:\Users\000487\Documents\visual studio 2012\Projects\BizTalk Server Project2\BizTalk Server Project2\bin\$(Configuration)</LocationPath></Orchestrations></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>
__
Is this a brand new BizTalk solution and projects created with BizTalk 2013, and a new Deployment Framework project created with the Add New Project wizard?__
as per your comments,
it is biztalk2013 sloution project, added the new Deployment Framework project to the project.
There is no settings file specified (/s:""").
_means?
i added setting file also._
This is my btdf file:
<?xml version="1.0" encoding="utf-8"?>
<!-- Deployment Framework for BizTalk 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>BizTalk Server Project2</ProjectName>
<ProjectVersion>1.0</ProjectVersion>
<IncludeSSO>False</IncludeSSO>
<IncludeMessagingBindings>True</IncludeMessagingBindings>
<UsingMasterBindings>True</UsingMasterBindings>
<RequireXmlPreprocessDirectives>True</RequireXmlPreprocessDirectives>
<ApplyXmlEscape>false</ApplyXmlEscape>
<IncludeSchemas>True</IncludeSchemas>
<IncludeOrchestrations>fasle</IncludeOrchestrations>
</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>420b521d-114d-4d02-b82a-5e7d6cbe0528</ProductId>
<!-- BizTalk App Version Upgrade -->
<ProductName>BizTalk Server Project2 for BizTalk</ProductName>
<Manufacturer>Deployment Framework User</Manufacturer>
<PackageDescription>BizTalk Server Project2</PackageDescription>
<PackageComments>BizTalk Server Project2</PackageComments>
<!-- NEVER change the ProductUpgradeCode. -->
<ProductUpgradeCode>97100c98-9858-4f75-9680-59e390dede91</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="BizTalk Server Project2.dll">
<LocationPath>C:\Users\000487\Documents\visual studio 2012\Projects\BizTalk Server Project2\BizTalk Server Project2\bin\$(Configuration)</LocationPath>
</Schemas>
</ItemGroup><!--<ItemGroup><Orchestrations Include="BizTalk Server Project2.dll"><LocationPath>C:\Users\000487\Documents\visual studio 2012\Projects\BizTalk Server Project2\BizTalk Server Project2\bin\$(Configuration)</LocationPath></Orchestrations></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>