-
Introduction We (that is Ray Houston and myself) want to introduce a new framework we developed in the past few months. This framework provides a fluent interface to Microsoft Silverlight . As we have been able to leverage a lot of OSS software in the past we found that it is time to give something back...
-
Introducing DI and “poor man’s DI” Introduction Greenfield Development happens when you start a brand new project, as in, clean slate development. No legacy code lying around, no old development to maintain. You're starting afresh, from scratch, from a blank slate, with no restrictions on what you're...
-
In the previous two posts I discussed the S of S.O.L.I.D. which is the Single Responsibility Principle (SRP) and the D of S.O.L.I.D. which corresponds to the Dependency Inversion Principle (DI). This time I want to continue this series with the second letter of S.O.L.I.D. namely the O which represents...
-
Introduction You may ask yourself why I publish another article about the single responsibility principle (SRP) . We already had some very good post about this principle at Los Techies, e.g. here , here and here to mention just a few. Well, the reason is that I consider this principle one of the most...
-
One common question when applying DDD is how to interpret other architecture’s concepts of a “model”. For example, two common presentation architectures are MVC and MVP. In each of those acronyms, the “M” is short for “Model”. So what exactly is this Model? Is it the Domain Model...
-
The Composite Design Pattern This post talks about the Composite Design Pattern and is part of Pablo's Topic of the Month - November: Design Patterns . A Composite is a tree structure where each node can be represented as a common type so that they can be acted on in a consistent manner, regardless of...
-
Pablo's Topic of the Month - November: Design Patterns Back in April, we announced we would be doing a PTOM on Design Patterns. It turned out that April was a busy month for all of us and we didn't live up to our announcement. I think we're going to claim it as a sad April fools joke. During the course...
-
I recently posted about enumeration classes , and how I like to use them as a sort of "Enumerations with behavior". Not every enumeration should be replaced with a class, but that pattern helps quite a bit when I find a lot of switch statements concerning my enumeration. Often, these strategies...
-
We made quite a bit of progress separating out the concerns in Part 2, but there are still some issues with our current design. Other parts in this series include: Separation of Concerns - how not to do it Separation of Concerns by example: Part 1 - Refactoring away from static class Separation of Concerns...
-
Pablo's Topic of the Month - April: Design Patterns Over the next few days and weeks, the Los Techies crew will be writing a number of blog posts focused a particular subject in addition to their regular blogging. Pablo's Topic of the Month for the month of April is about ' Design Patterns...
-
When developing with MonoRail , one of the common operations is to redirect to other controllers and actions. Originally, I looked at the BaseControllerTester to help test, but it required a little too much knowledge of the inner workings of MonoRail for my taste. Instead, I'll use a common Legacy Code...
-
When someone is using your code, you want your code to be as explicit and easy to understand as possible. This is achieved through Intention-Revealing Interfaces. Evans describes the problems of opaque and misleading interfaces in Domain-Driven Design : If a developer must consider the implementation...
-
It's interesting to see what other developers value and/or what topics they are interested in regarding the development of software. I'm going to start doing some internal presentations and live coding sessions at my company for my fellow consultants. I've got a pretty long list of possible...
-
Joe posed a great question on my recent entity validation post : I question the term Validator in relation to DDD. Since the operation of the Validator seems to be a simple predicate based on business rule shouldn't the term Specification [Evans Pg227] be used instead? On the surface, it would seem...
-
On the Yahoo ALT.NET group , an interesting conversation sprung up around the topic of validation. Entity validation can be a tricky beast, as validation rules typically depend on the context of the operation (persistence, business rules, etc.). In complex scenarios, validation usually winds up using...