Recently when creating a new BizTalk 2009 Orchestration I encountered a build error that I have not previously encountered. The Orchestration build error given was: Preprocessor directive must appear as the first token on a line After a small amount of investigation I discovered that the cause of this error was the Filter Expression that I had applied to the receive shape in my Orchestration. I had put: BTS.MessageType == http://targetnamespace#root... This should have been: BTS.MessageType == "http://targetnamespace#roo... ......

The following is effectively a repost of the BizTalk 2004 naming guidlines that I have previously detailed. I have posted these again for completeness under BizTalk 2009 and to allow an element of separation in case I find some reason to amend these for BizTalk 2009. These guidlines should be universal across any version of BizTalk you may wish to apply them to. General Rules All names should be named with a Pascal convention. Project Namespaces For message schemas: [CompanyName].XML.Schemas.[... ......

As stated in my previous post I am currently reading Richard Seroter's book "SOA Patterns with BizTalk Server 2009". Having just finished Chapter 1, Building BizTalk Server 2009 Applications, I thought I would record some immediate thoughts on what I have read so far. This chapter works as an introduction to BizTalk Server, covering the basic architecture, schemas, maps, messaging and orchestrations. While this is not likely to offer much to an experienced BizTalk developer, it does work as a good ......

I have recently picked up a copy of Richard Seroter's book "SOA Patterns with BizTalk Server 2009", and thought that I would try and make some useful comments on each chapter as I read it. I am currently working in an environment where we have been implementing BizTalk Solutions as a part of an overall SOA strategy for a number of years, and I am hoping that this book will help me to gain a new perspective on the use of BizTalk in this type of architecture, and hopefully expand my understanding of ......

The following BizTalk naming guidlines are heavily based on those proposed by Scott Colestock over at Trace Of Thought. As you can see from the link, Scott wrote his naming conventions for BizTalk Server 2006, whereas I am still using BizTalk Serevr 2004. In reality these guidlines are pretty much universal across any version of BizTalk you may wish to apply them to. Although the general principles for these guidlines are the same as Scott's, I have made some changes based on personal preference ......