Fix: In BizTalk Server 2006 R2, you cannot build a BizTalk Server project if the project refers to a schema and the first part of the schema namespace is a substring of the project namespace

Consider the following scenario in Microsoft BizTalk Server 2006 R2:

• You create a BizTalk Server project and you specify a default assembly namespace, such as XXX.YYY.
  
  Note The namespace is case-sensitive.
• You add a reference to an assembly in the project.
• You use a property schema from the referenced assembly to promote properties as property fields. You specify a schema namespace, such as YYY.ZZZ.
  
  Note The first part of the schema namespace, YYY, is a substring of the default assembly namespace, XXX.YYY.
• You try to build the BizTalk Server project.

In this scenario, you cannot build the project, and then you receive an error that resembles the following:For example, this problem occurs when you perform the following actions:

• You create a BizTalk Server project.
• You specify the default assembly namespace as the following:
  BTS.EDI.Schema
• You add a reference to the Microsoft.BizTalk.Edi.BaseArtifacts.dll assembly in the project.
  
  Note The Microsoft.BizTalk.Edi.BaseArtifacts.dll assembly is located in the installation folder of BizTalk Server. Usually, this location resembles the following:
  <drive>:\Program Files\Microsoft BizTalk Server 2006
• You use the EDI.PropertySchema property schema from the Microsoft.BizTalk.Edi.BaseArtifacts.dll assembly to promote properties as property fields.
  
  Note The first part of EDI.PropertySchema namespace, EDI, is a substring of the default assembly namespace, BTS.EDI.Schema.
• You try to build the BizTalk Server project.

In this scenario, you cannot build the project and you receive an error that resembles the following:

This problem occurs because BizTalk Server searches for the referenced schema only in the local assembly. For example, BizTalk Server only searches in the XXX.YYY assembly. However, BizTalk should search in the referenced YYY.ZZZ assembly. This causes the build failure.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have BizTalk Server 2006 R2 installed to apply this hotfix.

Restart requirement

You may have to restart the computer if the affected files are being used when you apply the hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about how to promote properties in schema project, visit the following Microsoft Web site:For more information about how to manage schemas within projects, visit the following Microsoft Web site:For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: