Export (0) Print
Expand All

How to Deploy a BizTalk Assembly from Visual Studio

[Unless specifically noted, the content in this topic applies to BizTalk Server 2013 and 2013 R2.]

This topic provides instructions on using Visual Studio Solution Explorer or the Visual Studio command prompt to deploy the BizTalk assemblies from Visual Studio into a BizTalk application. Although you can deploy a single assembly from the project level (such as by right-clicking the project and clicking Deploy) or deploy all of the assemblies in the solution at once from the solution level (such as by right-clicking the solution and clicking Deploy), we strongly recommend deploying all of the assemblies at once from the solution level.

With previous versions of BizTalk Server, if you wanted to deploy a multiple assemblies in a solution, and any of the assemblies had a dependency on any of the other assemblies, you had to individually deploy the assemblies in the reverse order of their dependencies. For example, if Assembly1 had a dependency on Assembly2, you had to deploy Assembly2 first, and then you could deploy Assembly1.

This is still the case when you deploy assemblies from the project level. With BizTalk Server 2013 R2, however, when you deploy assemblies from the solution level rather than the project level, BizTalk Server automatically takes care of all of the deployment steps, including deploying assemblies in the correct order. Therefore, to simplify deployment, when another assembly has a dependency on the assembly that you are deploying, you should deploy your assemblies at the solution level.

When you select the option to deploy a project or solution from within Visual Studio, the assembly or assemblies are automatically built and deployed into the specified BizTalk application in the local BizTalk group. If the application does not already exist in the group, deployment also creates the application. The assemblies and the artifacts they contain are registered and their data stored in the BizTalk Management (configuration) database for the BizTalk group. In addition, if you specify this option in deployment properties for the project, the assemblies are added to the global assembly cache (GAC).

An "artifact" is any item included in a BizTalk application, including resources you work with in Visual Studio, such as assemblies and orchestrations as well as other items you create or add later after deploying the application, such as send and receive ports, certificates, and scripts. After the assembly has been deployed, you can view and manage its artifacts in the Applications node of BizTalk Server Administration console. Each application is stored in its own folder, with subfolders displaying the artifacts in the application. For more information, see Using the BizTalk Server Administration Console. For more information about creating and managing applications, see Deploying and Managing BizTalk Applications.

Before you deploy an assembly, you must take the following steps:

You should never perform the tasks described in this topic on a production computer. During the development process, the developer often must redeploy assemblies from Visual Studio. To enable the redeployment, Visual Studio may undeploy, unbind, stop, and unenlist artifacts that exist in the same or different applications. Although this is necessary and appropriate in the development environment, it can cause unexpected and undesired consequences in a production environment. In addition, to avoid the possibility of anyone's attempting to deploy an assembly from Visual Studio on a production computer, we recommend that you not install Visual Studio on a production computer.

.NET Framework runtime security policy prevents deploying assemblies from a network share by default. If you attempt to deploy an assembly from a network share and experience difficulty, see your .NET Framework security administrator, or consult "Security Policy Management" in the Visual Studio Combined Collection.

To perform the procedures in this topic, you must be logged with an account that is a member of the BizTalk Server Administrators group. If, in Deployment properties, you have enabled the option to install an assembly to the global assembly cache (GAC), then you also need Read/Write permissions on the GAC. The Administrators account on the local computer has this permission. For more detailed information on permissions, see Permissions Required for Deploying and Managing a BizTalk Application.

Using Visual Studio Solution Explorer

  • In Visual Studio Solution Explorer, right-click a BizTalk project or solution, and then click Deploy.

    The assembly in the project or assemblies in the solution are deployed into the specified BizTalk application. The status of the build and deployment process displays in the lower left corner of the page.

Using the Visual Studio command prompt

  1. Start Visual Studio Command Prompt.

  2. Type the following command, substituting the appropriate values, as described in the following table:

    devenv /deploy SolnConfigNameSolutionName [/project ProjName] [/projectconfig ProjConfigName]


    devenv /deploy Release "C:\Documents and Settings\someuser\My Documents\Visual Studio\Projects\MySolution\MySolution.sln" /project "MyBizTalkApp\MyBizTalkApp.csproj" projectconfig Release


    Parameter Value


    Deploys a solution after a build or rebuild.


    Name of the solution configuration that will be used to build the solution named in SolutionName.


    Full path and name of the solution file.

    /project ProjName

    Path and name of the project file within the solution. You can enter a relative path from the SolutionName folder to the project file, or the project's display name, or the full path and name of the project file.

    /projectconfig ProjConfigName

    Name of a project build configuration to be used when building the project.

    The first time you deploy an assembly containing an orchestration, you may receive a warning message that the orchestration is not contained in the binding file. This is because orchestrations are not automatically bound to the host upon deployment. You must perform this step manually.

© 2014 Microsoft Corporation. All rights reserved.

Community Additions

© 2014 Microsoft