This blog post is about creating a BizTalk pipeline that allows the stream passed into it to be seekable. If the position of the stream is not reset when it’s returned then the message will be empty as the default stream is forward-only. [More]

In this demo I chose to highlight the artifacts that the BES project regards as warnings. These are the following: disabled orchestrations, disabled send ports and disabled receive locations. [More]

BizPhone is my contribution to the Sogeti mobile applications contest. It is built using BizTalk Explorer Services. The idea is that any service manager or developer can view the current status (and soon manage!) of a BizTalk server from anywhere using only their mobile device. [More]

The birth of BES came out of necessity for a BizTalk WCF API when I was working on a Windows Phone 7 project. I had taken a look at BizTalk Data Services by Tellago. But in the end I went down my own path in order to be in complete control and, honestly, the learning experience of it. [More]

This blog post is about validating data types in a BizTalk receive location. By default no data type validation is performed unless explicitly set. This approach could save a’lot of grief since the message is refused before it has the possibility of wreaking havoc in the BizTalk message box. [More]

This blog post is about routing error messages in BizTalk Server by filtering on ErrorReport.MessageType. Since BizTalk Server 2006 there’s the possibility of routing failed messages. This is enabled on the send port or receive port – not receive locations. [More]

After having installed Visual Studio 2010 on my 64-bit Windows 2008 server Enterprise Single Signed on stopped working. The event log tells us to call “regasm SSOSQL.dll” – which is very nice. Only it doesn’t work on 64-bit operating systems. [More]