Posts

Put together a little snippet to remind myself of the some of the beautiful language extensions that shipped with the C# language. {% highlight csharp %} namespace CSharpLanguageExperiment { using System; using System.Collections.Generic; using System.Linq; class Program { static void Main(string[] args) { // Object Initialiser Person bill = new Person { FirstName = “Bill”, LastName = “Gates”, Age = 40 }; // Type Inference var ben = new Person { FirstName = "Ben", LastName = "Simmonds", Age = 25 }; // Anonymous Types var john = new { FirstName = "John", LastName = "Smith", Age = 18 }; // Anonymous Delegate Func<string, bool> filter1 = delegate(string name) { return name.Length > 4; }; filter1("hel"); // Lambda Expression Func<string, bool> filter2 = x => x.Length > 4; filter2("foobar"); // Extension Method ben.GetData(); // Queries List<Person> people = new List<Person>(); people.Add(bill); people.Add(ben); Func<Person, bool> filter = x => x.Age > 30; IEnumerable<Person> exp = people.Where(filter); foreach (Person person in exp) { Console.WriteLine(person.GetData()); } } } ...

A few weeks ago I sat the 70-235 exam. Coming from a real-world perspective I wasnt overly impressed with the exam. To me it felt mind numbingly robotic and very 2006 R1 feature set focused (e.g. BAM and BRE). However the exam successfully probed some interesting areas within BizTalk, encouraging me to learn things about BizTalk that I would not otherwise get exposure to. Patrick Wellink’s post How to prepare for the BizTalk 2006 Exam concisely summarised how to prepare for this exam. At first I sensed some sarcasm in Patrick’s post, but now having successfully passed the exam found his post to be scaringly accurate. ...

BizTalk messages are very XML centric. A while ago there was a requirement to produce a neatly formatted XHTML report, which was destined to be emailed. At the time I stumbled across a customised version of the XslTransform pipeline component which ships with the BizTalk SDK. It demonstrates how to apply an XSLT transformation in the pipeline. The customised version I was playing around with, pulled up XSLT from a SQL data store. Regardless of where or how the transformation be done, we needed to produce an XHTML document as a result. The thing with XHTML is that is it just that. Its XML. A XSD schema can be produced from a well formed piece of XHTML. Therefore it is possible to create a strong message type (e.g. FooReport.xsd) which can then be pub/sub’ed with BizTalk. ...

Today while doing some vanilla BizTalk 2006 R2 installs, discovered the installer was choking with: Error 5003.Regsvcs failed for assembly C:\Program Files\Microsoft BizTalk Server 2006\Microsoft.BizTalk.Deployment.dll. Return code 1. Awesome. Other cases of a malfunctioning regsvcs executable have been reported. For reasons that remain unknown to me regsvcs.exe stop functioning following the installation of SP1 for VS.NET 2005 and the .NET 2.0. regsvscs.exe appeared to be intact, but invoking any of it functionality (including listing its command line help) would return nothing—hence the return code 1 problem. ...

Now my post-grad studies are finalised ive got some spare time to inject into technology. I plan to inject some solid hours into running through the .NET 3.0 certification stream. Some areas that currently excite me, which I hope to spend more time with: ASP.NET MVC Advanced Windows Debugging Azure/Oslo/Dublin BizTalk Server 2009 Claims Security and BizTalk JQuery JSON/POX WCF EndPoints MsBuild NServiceBus OpenId PKI and BizTalk PowerShell SharePoint Services UDP Multicast based Pub/Sub Engine Workflow Foundation

Microsoft has recently released a hotfix to enable font smoothing over remote desktop (RDP). If your addicted to font smoothing (aka ClearType) you will love this hotfix. At least Service Pack 1 is needed in order to install hotfix KB946633 on Windows Server 2003. On the client side you need at least RDC 6.0. In order for ClearType font smoothing to work it needs to be enabled per computer, on the remote desktop client and the user profile on the terminal server. ...

To provide a messaging infrastructure that will: Break the communication complexity problems associated with distributed software, such as the ability to deal with ongoing change, providing management mechanisms for the complex sea of distributed service interactions that typically take place in today’s IT environment. Provide reliable end-to-end messaging. Apply distributed software security. To provide a configurable, reusable architecture. Deal with common messaging problems generically—i.e. routing, transformation, exception handling and unification. Enforce consistency and unification. Leverage modern standards. Support legacy standards and interaction. Promote agility, through increased abstraction and loose coupling. Speed implementation turn-around, through configuration versus coding.

The goal of dynamic resolution is to avoid defining end-points anywhere statically. The responsibility of carrying and managing this knowledge, which is specific to the interaction, is frequently given to the consumer. That is, the consumer statically binds to the service endpoint/s that is consumes. If the responsibility be lifted from the consumer (or providers) itself, and given to an intermediate layer, such as the ESB, the byproduct are mechanisms for coping with change and dealing with infrastructural complexity. While the concept may appear to be trivial, its contribution toward providing a more managed distributed environment (many interacting end-points and data exchanges, etc) is significant. ...

Today I came across an interesting compile time error, given a scenario I had never exercised before. I had a vanilla orchestration that was receiving the same message type (same schema different message instance) using two different receive ports. I wanted to correlate the orchestration, so the first receive shape was set to activate with an “Initialising Correlation Set” and the second receive shape was set with a “Following Correlation Set”. This setup produced the following compile time error: ...

Lately I’ve been having heaps of fun playing with what’s known as the “ESB Guidance” (ESBG). A community/open source driven initiative as an attempt to fill the gap Microsoft currently have in the SOA/ESB space. At a high level it augments its existing messaging/integration engine, BizTalk Server, by adding extended functionality. The ESB guidance aims to: Demonstrate how to implement an ESB pattern using BizTalk Outline best practices Reduce the amount of “plumbing” clients would have to implement themselves Reduce the total cost and effort of an ESB implementation As of the November 2007 release it contains: ...