title: Separate the public/admin area in different asp.net mvc AREA's leads to double controllers?
body: <p>My site has multiple public pages showing some lists like news,products etc... everyone can see. So I have a NewsController and ProductController. The Create/Edit action can only be/must only be executed by the admin. When I separate the admin stuff (Create/Edit) from the public stuff(List) I would create 2 areas public/admin each having its own controller. That means I would have TWO ProductController one with List action and one with Create/Edit action and TWO NewsController same game...</p>
  
  <p>Would that make sense? I looks like DRY - don`t repeat yourself!</p>
  
  <p>How would you handle that scenario concerning the new asp.net AREA feature?</p>