title: What is a good way to build sub views with logic in ASP.NET MVC 3
body: <p>We're building a business application using Microsoft ASP.NET MVC 3.
  Some views are now becoming so complex that it seems reasonable to divide them into two or more separate views, with separate controllers and models. (Reuse is another reason for wanting to build separate views.)</p>
  
  <p>Which method do you recommend for achieving such separation in ASP.NET MVC?<br/>
  Partial Views seems like the obvious answer, but as I see it, partial views "out of the box" has little support for separate controllers.</p>
  
  <p>The best solution we've found so far is this, using the <br/>
  <code>Html.RenderAction("&lt;view initialization action method&gt;")</code><br/>
  method as explained here: <a href="http://www.primaryobjects.com/CMS/Article129.aspx" rel="nofollow noreferrer">http://www.primaryobjects.com/CMS/Article129.aspx</a></p>
  
  <p>This post also mentions the RenderAction method: <a href="https://stackoverflow.com/questions/705033/asp-net-mvc-correct-usercontrol-architecture">ASP .NET MVC correct UserControl architecture</a></p>
  
  <p>Do you see any weaknesses with this approach? <br/>
  Do you recommend any better, easier ways of achieving this?</p>