A builder separates the concern of creation of an object into an other object.
Its a great tool for testing ..
I am being frustrated in my attempts to abstract my business and model layers from each other by the cursed object typed parameter in framework methods
Say you want to store an array of strings associated with an entity using EF? For example Tags on a Blog Post...
When EF4 generates your db for a referenced object it uses the class name, which makes for confusion when there are more than one reference for the same type
I am aiming to be able to use interfaces to describe common objects in my data layer, so that I can have common/reusable business logic functions which can expect a certain interface
Did you know you can add a ValidationAttribute to an interface, and when this interface is used on a concrete class the validation is called?