When I was over at PDC the guys from GWB convinced me to move my blog to them (well, it didn’t take much convincing…), so I have, but I kept cross-posting on my old blog as well until I make up my mind. Took me way too long, but I have now decided to stick with my old place. Cross posting is naturally not a good idea, and I shouldn’t have done that ......

---

Briefly back on my STS work - Our STS implementation can already replace the authentication implementation of most of our applications; naturally we can’t do that just yet, given that the Geneva-framework has not been released yet, but all of my tests are quite positive so we’re just waiting for the opportunity to start using it. However, so far, we ......

---

This is a third post in a series describing my Oslo based solution for deploying BizTalk applications; I’ve used this exercise to play around with ‘M’, but it was important for me to work on a real solution, with real benefits – something I could actually use…in Part I I discussed the concept and presented both the “source code” of my app and the output ......

---

A few weeks back I worked on a process that looked something like this - It was triggered by the scheduled task adapter and then used a SQL send port to call SP to return list of ‘things’. It needed to split the things in the list to individual records, and to start a new, different, process, through pub/sub (to avoid the binary dependency with the ......

---

We’ve been slowly migrating our services from asmx to WCF, but as we’re still using BizTalk 2006 with no support for WCF we’ve been exposing endpoints configured for basicHttpBinding and consume them using the SOAP adapter. Generally speaking things have been going well, although we completely gave up on the idea of moving the services to WCF and NOT ......

---

From the Microsoft Knowledgebase - The <xsl:import> element is used to import an external XSLT file. The <xsl:include> element is used to include an external XSLT file. You cannot use these elements in custom XSLT files that are defined in the Custom XSL Path Grid Properties in a BizTalk project. You cannot do this because a Uniform Resource ......

---

A couple of weeks ago I published a post describing my Oslo based deployment framework for BizTalk. Two parts were missing from that post – the actual MGrammar and the runtime that processes the source code files. In this post I will go over the grammar I created for the framework; I will try to go over the complete grammar explaining the various steps, ......

---

In my notes on BizTalk 2009 post I have highlighted the fact that now, as part of the BizTalk installation, you can select the “Project Build Components” which allow you to build BizTalk projects without Visual Studio or BizTalk installed on the build machine. This is very cool feature of the product, but I have to admit that I have missed something ......

---

Since PDC I’ve been working on and off on an “Oslo” based solution for deploying a BizTalk application; unfortunately I couldn’t get a good chunk of time to play with this, so it’s been dragging a bit, but I’m getting close, so here are some details - I’m a big advocate of automated builds; it’s a topic that probably deserves a post of its own, so I ......

---

When you generate a class out of a schema with an element configured to allow mixed content (child attributes and elements as well as text), you should expect the corresponding generated field type to be a string array; So - if you have a schema that looks like this <?xml version="1.0" encoding="utf-8"?><xs... targetNamespace="http://tem... ......

---