Avoid Reserved Words In BizTalk Project Names

The post title seems intuitive, but I do this to myself roughly twice a year. The name of my BizTalk project will contain some sort of reserved word, and it causes me to waste all
sorts of time figuring out why BizTalk persecutes me so. Since this recent occurrence wasn't aided by any search engine results, I figured I'd contribute to them
for the next idiot.

This time, I had named my project "Microsoft.Demo.ZZZZ.BTS" and it had an orchestration in there. I'm reading out context values, so I have an expression
shape looking at "BTS.MessageID". Well, whenever I'd try to compile, I'd get Type or namespace name "MessageID" not found in assembly XYZ". After a few
minutes of brain cramping, I realized that since my default assembly namespace had the ".BTS" in it, the compiler couldn't resolve the MessageID context
property. So dumb of me. Once I changed my project/assembly/namespace name, everything worked fine. Moral of story, if you use namespace-style project naming like I do, make sure no parts of said name include words that will
trip up the BizTalk compilation.

Comments (2)
  1. Lucas Vogel says:


    You should strongly consider reading article "Developing Integration Solutions with BizTalk 2004" on MSDN (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/BTS_2004WP/html/ffda72df-5aec-4a1b-b97a-ac98635e81dc.asp). Among many other helpful topics, there is a sub-topic in there discussing naming conventions. It’s saved me from many additional headaches!

    Now if only someone would have warned me about BizTalk transactions and SQL Server… 🙂


  2. Yah, I’m very aware of this doc. It’s pretty darn useful. I just often end up putting my own flavor on it.

Comments are closed.

Skip to main content