I was at the MVP Summit just a few weeks ago and wanted to help publicize a few important fixes coming out of Redmond that can help your BizTalk development. Some hotfixes get combined into a rollup and others do not. Also, for some reason not all of the fixes make it into the KBAlertz that I subscribe to so you should periodically check around like at the BizTalk Customer Response Team blog (http://blogs.msdn.com/biztalkcrt/default.aspx
I was thinking through all of the recent ones I had downloaded and realized these would make a good top ten list. 🙂 I will make some comments along the way. Be sure to watch which version I reference because not all fixes apply to both 2006 R2 and 2009. Another good tip is to save the email for your hotfix password with your hotfix so you have the password for later. Passwords on hotfixes expire, saved emails do not. 🙂 Just make sure to encrypt that hotfix password file…
Here is the list (in reverse for fun):
9. On the forums I recently helped handle a situation for someone where the MQSC adapter was not working for 64-bit on BizTalk 2009. A hotfix had been released which overcame this problem on BizTalk 2006 R2 SP1: http://support.microsoft.com/default.aspx/kb/939202
The forum poster went ahead and installed the hotfix on their BizTalk 2009 server and it overcame the issue anyway, even though the hotfix was only targeted for BizTalk 2006 R2 SP1. Sometimes you can check the released version information on the hotfix to see if it matches with your server, but other times you just do not know the result of installing an older hotfix on a newer system.
6. When I worked on an EDI project there was an annoying problem where the GS02 and GS03 identifiers would get mixed up during the BizTalk EDI processing. This was resolved here: http://support.microsoft.com/kb/954557
5. This one is only really useful if you are working with VS 2010 RC and BizTalk vNext – Get intellisense back – http://support.microsoft.com/kb/980610
. Hopefully it gets applied in VS 2010 RTM and does not need to come to the world as a Windows Update.
3. If you have been using BizTalk 2009, you may have noticed some issues in VS when compiling and developing. I think these issues were introduced when the VS BizTalk extensions were updated to work with BizTalk 2009. Some people in the MVP community helped Microsoft identify and test out these issues. There are two fixes that are relevant to mention: http://support.microsoft.com/kb/977428
. I did not personally have this problem, but many expressed this was a problem for them.
2. The other VS issue for BizTalk 2009 hotfix was resolved with http://support.microsoft.com/kb/979153
. I encountered this one many times on larger projects, especially when using expression shapes in orchestrations.
1. Now for a really good one that everyone should install. I frequently encounter red herrings in doing diagnostic work and I am excited when hotfixes come out that actually solve the root problem. Here is one that clears up some compilation issues that surface as out of memory exceptions: http://support.microsoft.com/default.aspx/kb/975118
. This is a good one to install on both developer and server boxes.