sfeldman.NET

It is a great honour to work with the person who wrote the book I just recently finished reading. The Agile Samurai is a mix of project management and software development. It’s a reality check helper if you are trying to run agile process in your company/team/project. The intention of this post is not to review the book, this is what I will do later at Amazon. Jonathan has managed to make me think of certain things in a different manner, maybe a little bit more realistic. There are a few new tools I can put under my belt (Inception Deck) to move forward with. The most important message from the book IMHO was not taking Agile literally as written - fluctuate, experiment, and question.

This is not a technical post.

In my previous blog about consuming WCF service from BizTalk orchestration I wrote about how we’d invoke a service based on a document coming in and mapping it into the service request schema.

Today Developer Edition for BT2010 was announced. Great news for anyone who does BT development/testing.

Sometimes trivial things in .NET are not so trivial in the BizTalk world. Especially for standard .NET developers with the mindset for routine .NET development. Recently, I was asked to give a hand with a simple task that was surprisingly taking too long (and good that was asked for, why to waste time if you can leverage someone to give a hand – always something I resort to). On the web, there are plenty of resources, yet nothing emphasizes the little things that are obvious to somewhat experienced BizTalk-ers and is brand new to mature .NET developers. Lets dive into example.

I really like the concept. Wish Hudson build server would have this option…

I am looking at the code for Silverlight application and there’s something that just bugs me… INotifyPropertyChanged. This is not the first time, and yet again I see this interface implemented again, and again, and again. This violates several good principles (Single Responsibility and Duplicated Code). It also pollutes the code with cross cutting concerns (change notification). My choice of solution for this is simple – buy, do not build. Yes, it is possible to write a base class that would scan for a custom attribute and will do the wiring. But why? Why not to look into something like PostSharp and take advantage of the hard work the author(s) put into it to make it work.

For most of our projects we use StructureMap as a Container. Silverlight seems to change this a little. From preliminary review looks like StructureMap is not yet ready for Silverlight, so we started to look into a different container. The one that looked good was Ninject. Simple, straight forward, and elegant.