Muokkaa

Jaa


BizTalk ESB Toolkit Sample Applications

The ​Microsoft BizTalk ESB Toolkit includes several sample applications that you can install and run to see how the ESB works and how it uses some of the ESB pipeline components. You can adapt and modify the code and techniques used in the samples for your own applications.

Install the sample applications

  1. Create a folder named Projects in the root of your C: drive, and create a subfolder named Microsoft.Practices.ESB within this folder.

    Note

    In the current release, the supported installation is for the files to reside in the folder C:\Projects\Microsoft.Practices.ESB. The BizTalk binding files that ship with the samples depend on this path.

  2. When you install the ESB Toolkit, it includes a .zip file called ESBSource.zip in the installation location you specified (by default, C:\Program Files\​Microsoft BizTalk ESB Toolkit). Uncompress the ESBSource.zip file into the C:\Projects\Microsoft.Practices.ESB folder. This creates folders named Keys and Source that contain the sample key and the samples with source code. The Source folder contains the source code for the sample application, and the Keys folder contains the public keys used to sign the assemblies in the sample applications.

  3. Before you run the samples, remove the read-only attribute on the C:\Projects\Microsoft.Practices.ESB\ folder so that the samples install correctly.

  4. If you have not used PowerShell scripts before, you must open PowerShell as an Administrator and run the following command:

    set-executionpolicy unrestricted
    
  5. Open a command prompt as an administrator and run the following command to ensure WCF script maps are registered:

    C:\Windows\Microsoft.NET\Framework\v3.0\Windows Communication Foundation>ServiceModelReg.exe -r -y
    

Note

You need to open the ESBSource.zip file in order to get an access to the Samples code.

Sample applications

The following topics describe the sample applications and include additional installation instructions where applicable: