Yes of course once there are other controllers I will probably extract a common base class for this kind of functionality. However, you’re missing the point of my approach. At this stage we’re not making any assumptions about what we (think) we need, we’re doing the most simple steps to pass our tests. The common parlance for this is YAGNI or “you aren’t gonna need it”.

Of course, since we have a good suite of tests, we can confidently make these refactorings later when we need to. That is the whole point of TDD and the approach i’m taking! Thanks for your comments.

I think this is a great series of article, please keep it up, and the way you explain things is fantastic very simple and thorough
would you not agree that it s a good idea to add a BaseController where you do your CRUD

something like:

public class ControllerCRUD : SmartDispatcherController
{
public void List()
{

}

public void Add()
{

}
}

and then you inherit from that all your controllers?
also, do you think is a good idea to “add” the way you are adding?

if you are planing to use persistence and I m pretty sure you are going to be using AR for it is all that structure necessary?
Cheers
Andrea

Thanks for those great articles

Would you agree that I post french translations of them on my blog ? With credits to you of course

Cheers,

Gildas