Monday, January 04, 2010

Hotfix available for BizTalk 2009 and Visual Studio 2008

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!

ESB with UDDI on separate server - can this be done?

The answer to this is yes. To have the ESB Toolkit use a separate server, the server location must be changed in the esb.config file found in the installation folder of the ESB Install (not the bin folder). Change the url in the baseUri tag of the UDDI resolver element to the correct server.















However, if you want to add the esb binding information or publish a server to UDDI using the UDDIPublisher tool, you will need to copy the following files to the UDDI Server (all from the ESB Toolkit/bin directory):

Microsoft.Practices.ESB.ExceptionManagement.dll
Microsoft.Practices.ESB.UDDI3.dll
TransportTypes.xml
Microsoft.Practices.ESB.UDDIPublisher.exe
Microsoft.Practices.ESB.UDDIPublisher.exe.config

Place the files in the same folder, add the dlls to the GAC, and then run the UDDIPublisher.exe from a command line.