Azure DevOps CI-CD for BizTalk with BTDF and Powershell

In this blog, I would showcase a simple demo to deploy application with BTDF and Powershell scripts using Azure Devops CI-CD pipeline.

In the BizTalk solution, I added the power-shell scripts to the solution as shown below and customized the RunDeployment.ps1 script to be generic by taking in parameters(Application, Deployment Type and Environment),please refer this article for the power-shell scripts.

Refer below screen shot for CI Pipeline configuration. Here, I'm building the BizTalk solution and then with msbuild task we are building the BTDF project. Once we have the msi file, we are copying those binaries to the staging area and then packaging to the Azure Artifacts.

Refer below screen shot for CD Pipeline configuration, here we have added just power-shell task and configured the parameters.

In order to achieve CI-CD, I enabled the continuous integration and delivery options. Now, for every check-in against the master branch, BizTalk application would be deployed in corresponding environment.

BizTalk Deployment | BTDF Framework

In this tutorial, I would showcase a simple demo to deploy application using BTDF framework. BizTalk Deployment Framework (BTDF). This open source framework is often used to create installation packages for BizTalk Applications. Downloaded and installed BTDF on your box.


To the existing BizTalk project add Add a New Project under BizTalk Projects and select Deployment Framework for BizTalk Project, as shown

In Deployment Framework screen configure the artefacts you want to deploy and click the Create Project button, now the project file is created. Add  all the relevant files manually to the Deployment solution Folder.

Add  all the relevant files manually to the Deployment solution Folder. We have the Deployment project in place, add basic BizTalk artifacts to the Deployment project.

An ItemGroup is an element from MSBuild which is used by BTDF. Besides ItemGroups, you will also find PropertyGroups within the BTDF project file. PropertyGroups are used to organize all kind of parameters which can be used during deployment.

Add schemas, maps and orchestrations to the deployment project, follow below steps and repeat the same for each artifacts under respective element tags schema, transform and orchestraion.

In the Deployment project file, search for the ItemGroup that is used for deploying Schemas. It contains the text ‘<Schemas Include=”YourSchemas.dll”>’.

Replace ‘YourSchemas.dll’ with the name of the DLL which contains your schemas

The line with the ‘<LocationPath>’ tag, must contain the path where the DLL resides.

Now deploy the solution from VS as shown, but we see an error as it couldn't enlist the orchestration.

Open the BizTalk Server Administration Console and navigate to the application and bind the orchestration and logical ports. And export the bindings to generate master portbinding file.

Open SettingsFileGenerator.xml and add the environment related settings for each environment as shown.

For example use sendfilepath variable from the settings file in the PortBindingsMaster, you need to open the PortBindingsMasterFile.xml file, navigate to the Send Port which should use the addresses and replace the current address with ${sendfilepath}. Refer below screen shot.

Post setting up the binding, lets deploy the application from Tools-->Deployment Framework for BizTalk-->Deploy BizTalk Solution