title: Models in asp.net mvc 3 areas
body: <p>How to organize models in multiple areas ? I am trying to organize code using areas. I am using <strong>visual studio 2010 express</strong> , the project is on <strong>asp.net mvc3</strong> and <strong>code-first development</strong> is used. All the tutorial and reference over internet only talks about controllers and routes, but what about models ? more precisely, I am looking for suggestions around :</p>
  
  <ol>
  <li>The model folder in an area will contain its own classes, so where
  should the dbcontext be placed ? I already have an dbcontext class
  containing multiple dbset entries in the "root" model folder. Can i
  have multiple dbcontext storing its data in the same database ?</li>
  <li>I have gone through asp.net mvc portable areas project by
  mvccontrib, but its still in asp.net mvc2, but is that the only way
  around for building plugins/components in asp.net mvc 3 ?</li>
  <li>Apart from areas/portable areas, is there any better way to organize
  code is such a way that new features can be simply "dropped-in",
  without doing too much changes in existing code ? Areas looks
  promising but i am not able to figure out how models should be
  placed.</li>
  <li>Are areas only good for controller and view separation ?</li>
  </ol>