IoC containers are great at reducing complex dependencies in an application and the Dependency Injection design pattern has existed for quite some time. Although IoC containers are quite popular in the Java world but it’s taken some time for good IoC containers to emerge for .Net. Even MS has jumped on the bandwagon and is showing some love for IoC by giving us Unity as an IoC container. Today there are many, many IoC containers to choose from. That’s the one thing I really like about the ALT.Net community, varied implementations and depth of choice that allows us to...

[Edit: Fixed the url to the source code.In my previous post, Implementing Repository and Specification patterns using Linq, I implemented a Repository pattern that allows consumers of the repository to use Linq to query the repository. Along with implementing a Repository pattern I also implemented a pattern for defining Specifications that could be used by not only Domain objects but also can be used with the Repository implementation for querying. In response to that post, there were a number of comments regarding how the RepositoryBase could be used to implement a Repository for Linq to SQL and also questions...

Well so far I’ve gone without making any specific decisions on the the infrastructure that Rhinestone will depend on and what kind of architecture will I use to design and implement the app. Out with the old, in with the new For the most part, all my previous projects, be it commercial or for hobby, have followed the traditional layered architecture where an application is broken down into layers; UI, Business layer, Data Access, etc., where dependencies flowed downwards. Meaning the UI components could only call components in the Business Layer and so on so forth. Violating the...

[Edit: Fixed spellings] Jeffery Palermo has a post up on his blog proposing a new kind of architecture… the Onion architecture. The formalization of this architecture has been a long time coming. I completely believe that with mature Inversion of Control tools and Dependency Injection patterns, its time to ditch the old layered application architecture. Looking at the Onion architecture, as proposed by Jeffery, one would think its just an abstraction of the Tiered architecture but the core difference between the two is how dependencies and infrastructure is treated in the Onion Architecture. In traditional Tiered-Layer-Architecture, each layer directly depends...