title: My ASP.NET MVC application is Anemic
body: <p>I read Fowlers description of Anemic Domain and I believe I have those symptoms. I have several objects doing nothing but passing data around in different packages. I also have several Services that pretty much handle all the behavior (executive functioning). I am starting to lose track of why and what i did and where to find certain tasks. </p>
  
  <p>The application does what I want, but i wonder if i just have a procedural program in oo disguise. Perhaps I can never shake my procedural programming past? should I?</p>
  
  <p>In MVC, Should I eliminate my services and spread that responsibility to my Controllers and Model Objects?</p>
  
  <p>I appreciate analogies between MVC concepts and DDD conepts...</p>