Checklist: Updating an Assembly

The following checklist describes the process of updating one or more artifacts in an application that has already been deployed, and then redeploying the application.

If you cannot schedule downtime or have very long-running instances that cannot be terminated, update using side-by-side versioning.

Steps Reference

Review the important considerations for updating artifacts in an application.

Ensure that you have appropriate permissions to perform the deployment.

Permissions for Managing an Application

Make any necessary changes to your assemblies, adding, removing, or reconfiguring artifacts as required.

Deploy the assemblies from Visual Studio into a BizTalk application in the development environment.

Test any new or changed artifacts, ensuring that any artifacts that may depend on the new or changed artifact are also tested.

When testing, be sure to consider dependencies that may exist between this application and other applications.

"Testing Tasks for BizTalk Application Deployment" in BizTalk Server 2009 Help at

In the BizTalk Server Administration console, add, remove, or reconfigure artifacts in the application as necessary.

Export the application containing the new or changed artifacts into an .msi file.

If the update will interfere with the application as it runs, schedule downtime, and stop the application that you want to update.

Import the changed or updated artifacts from the .msi file into the application that you want to update, installing the application.

When you update a BizTalk assembly, you should stop and unenlist artifacts before importing from the .msi file. You should re-enlist and then start BizTalk artifacts after you import from the .msi.

Start the application, resuming message publication. Restart all BizTalk host instances.

After importing an assembly that contains an orchestration, if the application to which you are importing it already contains an assembly that has the same name, public key token, and version, stop and start the host instances of the host to which the orchestration is bound. This ensures that the new version of the assembly is used by BizTalk Server.