Installing the ESB Toolkit 2.1 on BizTalk 2010 R2 - July 2012 CTP

In the "Building Integration Solutions using BizTalk On-Premises and on Azure" on TechEd 2012 ( is noted “ESB Toolkit as core part of BizTalk setup and product”. So I was very curious if the ESB toolkit already is implemented in the July 2012 CTP release of BizTalk 2010 R2. After configuring the BizTalk 2010 R2 virtual machine in Windows Azure I searched for the ESB toolkit but it’s not a part yet of the BizTalk setup and not on the VM. But why not installing the ESB Toolkit 2.1?



Installing the ESB Toolkit on a BizTalk machine is sometimes a challenge. I've followed the instructions of the ESB Toolkit installation guide to install the core components so I do not go into the details,.

1) Install the ​”BizTalk ESB Toolkit 2.1-x64.msi” to install the ​Microsoft BizTalk ESB Toolkit and the necessary registry entries

ESB toolkit setup

2) Import the "Microsoft.Practices.ESB.CORE64.msi" in the BizTalk Server Administration Console


3) Configure the BizTalk ESB Toolkit Core services and components with ESB Configuration Tool in the bin directory (ESBConfigurationTool.exe)

ESB configuration tool

4) Install the from the installation location to install the ESB Toolkit Sample Applications

Test the ESB Toolkit installation

To test the installation I used a small BizTalk project with 2 schemas and a map to create a BizTalk application. To send a message to one of the on-ramps that are provided by the BizTalk ESB Toolkit I used the sample “GlobalBank.ESB.Samples.Itinerary” application.

You can open the sample with Visual Studio 2012 and upgrade the projects in the solution to the new version of Visual Studio.


Run the Itinerary Test Client to send a message with an itinerary to the ESB.ItineraryServices on-ramp.


Test Results

First the good news, it is possible to install the ESB Toolkit 2.1 on BizTalk 2010 R2 and you can use it to route a message to an off-ramp. I think it’s also possible to use orchestrations to extend the ESB toolkit but I didn't test that feature. But the bad news is that you can’t use maps to transform a message! I got the following error when I used the TransformationService in an itinerary:

Method not found: 'System.Xml.Xsl.XslTransform Microsoft.XLANGs.RuntimeTypes.TransformMetaData.get_Transform()'.

Source: Microsoft.Practices.ESB.PipelineComponents.DispatcherDisassemble

I compared the “get_Transform()” method in the old and the new Microsoft.XLANGs.RuntimeTypes.TransformMetaData assembly and the signatures are not the same!

The return value in BizTalk 2010 is “XslTransform” and in BizTalk 2010 R2 it's “XslCompiledTransform”. The ESB toolkit 2.1 expects the old type resulting in the “Method not found” error.

To cut a long story short, We will have to wait for a new CTP!

About the author

Tomasso Groenendijk lives in Netherlands and is a Solution Architect at Insight. He has over 20 years experience in software development and software design. Tomasso is specialized in application integration with a strong interest in the Windows Azure cloud platform. From 2014, Tomasso has been awarded six times with the Microsoft Azure MVP award. He is an active contributor to the integration community through his work on his blog, GitHub samples, TechNet Wiki and speaking on events. Furthermore he is an official board member of the Dutch Microsoft Integration User Group.

MVP profile Tomasso Groenendijk
Sentinet Product Specialist
BizTalk360 Product Specialist

Month List