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.

Note

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. - Important Considerations for Updating Applications (http://go.microsoft.com/fwlink/?LinkId=154823).
- Best Practices for Updating Applications
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.
- How to Update an Assembly
- Updating an Artifact
- “Updating an Artifact" and "Updating an Assembly " sections of Best Practices for Updating Applications
- How to Deploy a BizTalk Assembly from Visual Studio (http://go.microsoft.com/fwlink/?LinkId=154824).
Test any new or changed artifacts, ensuring that any artifacts that may depend on the new or changed artifact are also tested. Note: When testing, be sure to consider dependencies that may exist between this application and other applications. Testing Tasks for BizTalk Application Deployment (http://go.microsoft.com/fwlink/?LinkId=154825).
In the BizTalk Server Administration console, add, remove, or reconfigure artifacts in the application as necessary. - How to Create or Add an Artifact (http://go.microsoft.com/fwlink/?LinkID=154724).
- How to Remove an Artifact from an Application (http://go.microsoft.com/fwlink/?LinkID=154688).
- Managing Artifacts (http://go.microsoft.com/fwlink/?LinkID=154725).
- Updating an Artifact
- "Updating an Artifact" section of Best Practices for Updating Applications.
Export the application containing the new or changed artifacts into an .msi file. - Exporting BizTalk Applications, Bindings, and Policies (http://go.microsoft.com/fwlink/?LinkId=154826).
- How to Export an Application to an .msi File
- "Exporting a BizTalk Application" section of Best Practices for Deploying an Application.
If the update will interfere with the application as it runs, schedule downtime, and stop the application that you want to update. - How to Start and Stop a BizTalk Application (http://go.microsoft.com/fwlink/?LinkID=154729).
- “Starting or Stopping an Application” section of Best Practices for Updating Applications.
Import the changed or updated artifacts from the .msi file into the application that you want to update, installing the application. Note: 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. - How to Import a BizTalk Application (http://go.microsoft.com/fwlink/?LinkId=154827).
- How to Import an Application from an .msi File
- "Importing a BizTalk Application" section of Best Practices for Deploying an Application.
- How to Install a BizTalk Application (http://go.microsoft.com/fwlink/?LinkID=154728).
- How to Install an Assembly in the GAC (http://go.microsoft.com/fwlink/?LinkId=154828).
Start the application, resuming message publication. Restart all BizTalk host instances. - How to Start and Stop a BizTalk Application (http://go.microsoft.com/fwlink/?LinkID=154729).
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. - How to Stop a Host Instance (http://go.microsoft.com/fwlink/?LinkId=154829).
- How to Start a Host Instance (http://go.microsoft.com/fwlink/?LinkId=154830).