Into the Fray

September 25, 2009 · 1 min read

This is my first attempt at writing a blog, so you may have to bare with me as I try to find both my feet and the time to get things started properly.

My main reason for starting this blog is to keep a track of the useful articles, information and golden nuggets that I come across in my daily routine at work as BizTalk developer.

Unfortunately we are currently stuck on BizTalk 2004, which as some of you may know is now three versions out of date.  As such, many of the better BizTalk resources are no longer actively commenting on or investigating this version, and the useful information that is out there tends to be hidden behind a raft of similar content for BizTalk 2006, 2006 R2 and now 2009!

I hope that by starting this blog I can try and collate some of the useful resource I have found into one place for my own future reference, but also for anyone else out there who is also still using the 2004 version of BizTalk.

My history as a BizTalk developer goes back a few years to a period when I started working on BizTalk 2000 solutions for a financial organisation in England.  Prior to this I had experienced a number of languages and development environments, but since this time have mainly been involved in the world of BizTalk; working with BizTalk 2004 for the last five years or so.

This article is part of the GWB Archives. Original Author: Stuart Brierley

New on Geeks with Blogs

  • We Won The One Award I Actually Care About

    Full Scale made the Inc. 5000 for the fifth year straight, the 12th listing across my three companies. Here is why the one award you cannot buy is worth stopping for.

  • Your Customers Build the Features Now

    I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.

  • Get the Size of a Directory in Linux the Easy Way

    du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

  • Vim Search and Replace: The Ultimate Guide

    One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.