January 3, 2008

If you are at the edge of learning BizTalk Server, check out the issues that come out of this elegant resource – they call it BIZTALK HOTROD. Their 3rd issue is out recently and they had their 1st and 2nd issues released in the past.

Cool stuff – find it here.


When I was implementing the Failed Message Routing feature in BizTalk Server 2006, I got caught up into the notion that Failed Orchestration Routing may execute the same way as Failed Message Routing. Turned out that they don’t – Failed Message Routing and Failed Orchestration Routing are two different notions. BTS 2006 can only handle Failed Message Routing by enabling the flag “Enable routing for failed messages” on either a Send or a Receive port. If you ever need to handle Failed Orchestration routing, then you will need to implement the exception logic in the orchestraiton and fill in the ErrorReport promoted properties for the Error Report Orchestration to subscribe the Failed Message from an Orchestration.

Here is a good blog by Matt Meleski around this notion:

gacutil /l [Assembly Name]

December 10, 2007

Quick tip on how to find the full Assembly name in .Net. This comes handy when you are trying to use the full Assembly name in scenarios like Dynamic Transforms in BizTalk where you will need to give the full Assembly name as a parameter.

You can use command “gacutil /l [Assembly Name]” in the Visual Studio .NET command prompt and get the full assembly name which outputs the name in this format:

BT.Schemas, Version=, Culture=neutral, PublicKeyToken=edbffc61eb1e7821, processorArchitecture=MSIL

Then, you can mark the section in the command prompt and copy-paste. Hope this may come handy for you at some point.

MS SOA and BPM Conference

August 31, 2007

MS BPM Conference coming close.

Here is the link:

BizTalk Server 2006 R2

August 30, 2007

Excited to hear BizTalk team is coming out with BizTalk Server 2006 R2 soon.

Check out the link below.