HI,

For all who is using BTDF this is a wonderful script to do silent BTDF installation.

After using that script i got below exception.Do any one have any ideas of what this exception means from BTDF side.

Am using BTDF 6.0 version,BTS 2013 r2 version.
Could you please tell me how to get rid of this exception


Target InitWixDir:
    Using WiX Install Path 'C:\Program Files\test\Deployment\Developer\WiX'.
Target Clean:
    C:\Program Files\test\Deployment\Framework\BizTalkDeploymentFramework.WiXSetup.targets(198,5): error : Cannot continue. The OutputPath property is undefined. By default, this property is defined in the .btdfproj in PropertyGroups conditional to Debug and Release configurations.
Done building target "Clean" in project "Deployment.btdfproj" -- FAILED.

Done building project "Deployment.btdfproj" -- FAILED.

Build FAILED.

C:\Program Files\test\Deployment\Framework\BizTalkDeploymentFramework.WiXSetup.targets(198,5): error : Cannot continue. The OutputPath property is undefined. By default, this property is defined in the .btdfproj in PropertyGroups conditional to Debug and Release configurations.
    0 Warning(s)
    1 Error(s)

Hi Sandy,

You need to right click the Solution and set the Build Configuration to either Debug or Release.

Rachit

HI,

its set to debug mode only..

This issue is nothing to do with your Powershell script which triggers the BTDF. This issue is to do with BTDF configuration.

Can you just deploy the BTDF using your Visual Studio directly, without using Powershell first? Ensure your BTDF configuration works first. Also ensure you build the solution first. The sequence I normally follow with BTDF in Visual Studio is as follows:

• Build
• Rebuild
• Undeploy
• Build Server deploy
• Deploy

I suggest this as this error normally occurs when the script doesnt find the built msi.

Regards,

M.R.Ashwin Prabhu

HI Aswin,

Yes my .btdf worked, below is my BTDF file.

normal installation is fine, issue happens only when using powershell.

Am using BTDF 6.0

<?xml version="1.0" encoding="utf-8"?>
<!-- 
  Deployment Framework for BizTalk
  Copyright (C) 2008-14 Thomas F. Abraham, 2004-08 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>BiztalkApp</ProjectName>
    <ProjectVersion>1.0</ProjectVersion>
   <IncludeComponents>True</IncludeComponents>
	  <IncludeSchemas>True</IncludeSchemas>
	  <IncludeTransforms>True</IncludeTransforms>
	  <IncludeOrchestrations>True</IncludeOrchestrations>
	  <IncludePipelineComponents>False</IncludePipelineComponents>
	  <IncludeSSO>True</IncludeSSO>	 
    <IncludePipelines>True</IncludePipelines>
	  <UsingMasterBindings>True</UsingMasterBindings>
	  <RequireXmlPreprocessDirectives>False</RequireXmlPreprocessDirectives>
	  <EnableXmlPreprocess>True</EnableXmlPreprocess>
    <SkipIISReset>True</SkipIISReset>    
  <EnableAllReceiveLocationsOnDeploy>False</EnableAllReceiveLocationsOnDeploy>
  
  </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.2</ProductVersion>
    <ProductId>ea94690e-291d-4ac7-abc1-5b6cb19327ad</ProductId>
    <!-- BizTalk App Version Upgrade -->
    <ProductName>BiztalkApp for BizTalk</ProductName>
    <Manufacturer>Deployment Framework User</Manufacturer>
    <PackageDescription>BiztalkApp</PackageDescription>
    <!-- NEVER change the ProductUpgradeCode. -->
    <ProductUpgradeCode>1da444c7-f69e-44db-b97c-4d12f99a8b9c</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>
  </PropertyGroup>
  <PropertyGroup Condition="'$(Configuration)' == 'Release'">
    <DeploymentFrameworkTargetsPath>$(MSBuildExtensionsPath)\DeploymentFrameworkForBizTalk\5.0\</DeploymentFrameworkTargetsPath>
    <OutputPath Condition="'$(TeamBuildOutDir)' == ''">bin\Release\</OutputPath>
    <OutputPath Condition="'$(TeamBuildOutDir)' != ''">$(TeamBuildOutDir)</OutputPath>
  </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>false</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>
    <Components Include ="BiztalkAppHelper.dll">
      <LocationPath>..\BiztalkAppHelper\bin\$(Configuration)</LocationPath>
    </Components>
   <Schemas Include ="AppProjectSchemas.dll">
      <LocationPath>..\AppProjectSchemas\bin\$(Configuration)</LocationPath>
    </Schemas>
   <Pipelines Include ="AppProjectPipelines.dll">
      <LocationPath>..\AppProjectPipelines\bin\$(Configuration)</LocationPath>
    </Pipelines>
   <Transforms Include ="AppProjectTransforms.dll">
      <LocationPath>..\AppProjectTransforms\bin\$(Configuration)</LocationPath>
    </Transforms>
    <Orchestrations Include ="AppProjectOrchestations.dll">
      <LocationPath>..\AppProjectOrchestations\bin\$(Configuration)</LocationPath>
    </Orchestrations>
  </ItemGroup>
  <ItemGroup>
		<AppsToReference Include="BizTalk EDI Application"/>
  <AppsToReference Include="Shared"/>
	</ItemGroup>
  <!-- !!! TODO !!! -->
  <Import Project="$(DeploymentFrameworkTargetsPath)BizTalkDeploymentFramework.targets" />
  <Target Name="GetEnvironmentName" Condition="'$(Configuration)' == 'Server'">
    <PropertyGroup>
      <SettingsFileOffset>9</SettingsFileOffset>
      <EnvironmentOffset>$([MSBuild]::Add($(SettingsFilePath.IndexOf('Exported_')), $(SettingsFileOffset)))</EnvironmentOffset>
      <EnvironmentLength>$([MSBuild]::Subtract($(SettingsFilePath.IndexOf('Settings.xml')), $(EnvironmentOffset)))</EnvironmentLength>
      <EnvironmentName>$(SettingsFilePath.Substring($(EnvironmentOffset), $(EnvironmentLength)))</EnvironmentName>
    </PropertyGroup>
    <Message Text="EnvironmentName: $(EnvironmentName)"/>
  </Target>
<Target Name="CustomRedist">
  </Target>
</Project>

HI guys,

Thanks to all for spending time especially Mr Ashwin.I got the solution from that post comments.

once again thanks to Randy..

The posted solution is missing a parameter: /target:Deploy

So if you change line #150 to this, it works like magic.
$args = /p:{1} /target:Deploy /l:{2} {0} -f $btdfFile,$parms,$logger

• Marked as answer by sandydv85 19 hours 49 minutes ago

HI guys,

Thanks to all for spending time especially Mr Ashwin.I got the solution from that post comments.

once again thanks to Randy..

The posted solution is missing a parameter: /target:Deploy

So if you change line #150 to this, it works like magic.
$args = /p:{1} /target:Deploy /l:{2} {0} -f $btdfFile,$parms,$logger

• Marked as answer by sandydv85 Monday, February 16, 2015 3:35 PM

HI guys,

Thanks to all for spending time especially Mr Ashwin.I got the solution from that post comments.

once again thanks to Randy..

The posted solution is missing a parameter: /target:Deploy

So if you change line #150 to this, it works like magic.
$args = /p:{1} /target:Deploy /l:{2} {0} -f $btdfFile,$parms,$logger

• Marked as answer by sandydv85 Monday, February 16, 2015 3:35 PM

Hi,

I am getting same error when using BTDF 5.0, VS 2010, TFS 2010.

Could you please confirm in which target do we have to add this line.

Thanks,

Ankur