.NET Assemblies

To deploy one or more assemblies that contain custom .NET code (a.k.a. components), edit your Deployment Framework for BizTalk project file (.btdfproj) as follows:

1. Set the IncludeComponents property to true

The property may be included in any PropertyGroup, but is commonly placed in the first PropertyGroup in the project file.

<PropertyGroup>

 ...

 <IncludeComponents>true</IncludeComponents>

 ...

</PropertyGroup>

2. Add a Components ItemGroup

The following is a typical example that properly follows the common ItemGroup structure:

<ItemGroup>

 <Components Include="$(ProjectName).Components.dll">

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

 </Components>

</ItemGroup>

The following is the default configuration, which corresponds to the optional naming conventions.  This default is in effect if you do not include any Components elements in your project file.

<ItemGroup>

 <Components Include="$(ProjectName).Components.dll">

   <LocationPath>..\$(ProjectName).Components\bin\$(Configuration)</LocationPath>

 </Components>

</ItemGroup>

If you have more than one assembly that contains custom .NET code, then repeat the <Components> element for each assembly (usually within the same ItemGroup).

NOTE: If you are deploying a third-party assembly that must be deployed to the GAC but does not have source code within your solution, then place it in an ExternalAssemblies ItemGroup.

Created with the Personal Edition of HelpNDoc: Easily create Web Help sites