Comments on: asp.net mvc -> the rise of the messy controllers http://www.chrisvandesteeg.nl/2007/12/14/aspnet-mvc-the-rise-of-the-messy-controllers/ What's practical is logical Thu, 24 Jun 2010 14:10:10 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Wöchentliche Rundablage: ASP.NET MVC, ADO.NET Dataservices ("Astoria"), ASP.NET, LINQ, WPF | Code-Inside Blog http://www.chrisvandesteeg.nl/2007/12/14/aspnet-mvc-the-rise-of-the-messy-controllers/comment-page-1/#comment-23842 Wöchentliche Rundablage: ASP.NET MVC, ADO.NET Dataservices ("Astoria"), ASP.NET, LINQ, WPF | Code-Inside Blog Mon, 17 Dec 2007 19:05:25 +0000 http://www.chrisvandesteeg.nl/2007/12/14/aspnet-mvc-the-rise-of-the-messy-controllers/#comment-23842 [...] ASP.NET MVC - The rise of messy controllers [...] [...] ASP.NET MVC – The rise of messy controllers [...]

]]> By: Jonathan Holland http://www.chrisvandesteeg.nl/2007/12/14/aspnet-mvc-the-rise-of-the-messy-controllers/comment-page-1/#comment-23741 Jonathan Holland Fri, 14 Dec 2007 16:07:54 +0000 http://www.chrisvandesteeg.nl/2007/12/14/aspnet-mvc-the-rise-of-the-messy-controllers/#comment-23741 The beauty of ASP.NET MVC is that they don't force any one model on your. What you really want to do is move all of your proprietary ORM dependedant code into the model, so in the worst case, changing ORM's is just a rewriting the model. Never put that stuff in the controllers. Your breaking the DRY principle. The beauty of ASP.NET MVC is that they don’t force any one model on your. What you really want to do is move all of your proprietary ORM dependedant code into the model, so in the worst case, changing ORM’s is just a rewriting the model.

Never put that stuff in the controllers. Your breaking the DRY principle.

]]>