If you have developed with BizTalk 2009 and Visual Studio its a safe bet that you have encountered the error(s) where one BizTalk project suddenly loses the reference to another BizTalk project. When looking at the project references for Project A, you can still see the reference to Project B, but the orchestration is complaining that it cannot find the schema, or the map cannot find the destination schema, etc. The solution was to either switch the "Copy Local" value to False then switch it back to True. Or - and I found this to work better - to delete and re-add the reference.
I am glad to announce that there is now a hotfix for this issue (KB 977428):
FIX: You experience various problems when you develop a BizTalk project that references another BizTalk project in Visual Studio on a computer that is running BizTalk Server 2009
Go and get it!
Subscribe to:
Post Comments (Atom)
Posts
No comments:
Post a Comment