Assemblies with a common name in a common namespace may not appear in a BizTalk Server 2004 project in Visual Studio .NET 2003 (839452)
The information in this article applies to:
- Microsoft BizTalk Server 2004 Developer Edition
- Microsoft BizTalk Server 2004 Enterprise Edition
- Microsoft BizTalk Server 2004 Partner Edition
- Microsoft BizTalk Server 2004 Standard Edition
SYMPTOMSWhen you work in Microsoft BizTalk Server 2004 with orchestration in Microsoft Visual Studio .NET 2003, and when you have assemblies that share a name in a namespace in your Solution, only one of the namespace and assembly combinations may be available for selection.CAUSEThis issue occurs when you reference multiple assemblies that share the same namespace. In this situation, the first assembly that is added added to the solution appears but additional assemblies that contain the same name in the namespace may not be available for selection. If two assemblies share a class name in a common namespace, you can only reference the first assembly with that class name because Visual Studio .NET 2003 cannot determine the assembly that you want. For example, this situation may occur if you follow these steps: - You create a new solution in Visual Studio .NET 2003.
- You add a minimum of two projects with a common namespace and a common class name, and then include you the two projects in the solution by reference.
- You add a BizTalk Server 2004 project to the solution, and then you add an orchestration to the project.
In this situation, if you declare a variable and then select Variable type, only the first assembly that you add to the project appears in the list of available assemblies. RESOLUTIONTo resolve this issue, use one of the following methods: - Rename one of your classes so that each class has a unique name.
- Create a secondary namespace before each class name
| Modification Type: | Major | Last Reviewed: | 4/23/2004 |
|---|
| Keywords: | kbBug kbnofix kbBTSOrchestration KB839452 kbAudDeveloper kbAudITPRO |
|---|
|