You may also want to consider how you should approach versioning other types of BizTalk components such as orchestrations that aren't long running, maps, pipelines, .NET helpers, WCF behaviors, or even pipeline components and mapping functoids. When it boils down to it, these are really just .NET assemblies and thus can be approached with a similar versioning strategy you'd follow for regular .NET assemblies with a few extra considerations.

The two paths you would typically take would be to increment the .NET assembly version and deploy the updated assembly alongside the existing assembly as detailed when discussing versioning long-running orchestration, or to overwrite the existing assembly while incrementing the file version, which will be discussed shortly.

One of the most important points you need to consider when deciding how to version these components is whether the change you're making is targeted at all the components that reference the updated...