BizTalk.... sigh...
BizTalk 2006 (BTS06) is pretty much BTS04, but with all the configuration- and administration utilities that BTS04 always lacked. With BTS04 we had to use tools such as
Paul Somers' awesome
BizTalk 2004 Management Tool. (For a list of cool BTS04 stuff, go
here).
The BTS04 core engine does a fine job, once you can get it doing what it should, but there were never any tools to get it doing just that. So you'll think that, since BTS06 has all the tools BTS04 lacked, coupled with the (good) BTS04 engine, it should be one wicked piece of machinery.
You can open BTS06 projects only with VS2005 (and not VS2003). That's pretty cool, because it means that you can integrate your BTS projects into your development environment using standard tools like MSBuild / VSTS. Wait a minute!!! Have a closer look - why is the .btproj (BizTalk project-file) still in the format of the VS2003 project-files? This means that MSBuild has no clue what this is, and thus can't build it!!!
At least now you can deploy BTS bits using MSI packages. With BTS04, the only way you could install was by using VS2003, and we all know how much most companies want to buy VS2003 and get that installed in their production environments. Creating an MSI package to help ship your bits sounds really welcome! Wait another minute!!! How do I create the MSI package?! I need to install the bits, using VS2005, to the BTS server, and then export the MSI package from the server!!! Brilliant!!! The MSI thus serves as no more than a convenient way to restore a previously installed BTS server.
(I would love to get my hands on what it is the BTS guys smoke).
There are some cool things about BTS2006, however:
- The btstask.exe cmd-line tool
- The Configuration Tool
- The Administration Tool
- The Flat-file schema wizard
- The BTS "Application" concept
Admittedly I am brand-spanking new in the BTS world, I keep wondering if I am missing something very obvious; these problems are unacceptably ridiculous!