title: ASP.NET Core Razor pages vs Full MVC Core
body: <p>There has been a question at SO <a href="https://stackoverflow.com/questions/46777404/why-is-razor-pages-the-recommended-approach-to-create-a-web-ui-in-asp-net-core-2">Why is Razor Pages the recommended approach to create a Web UI in Asp.net Core 2.0?</a> where Steve Smith has kindly explained the benefits of using Razor Pages over full MVC from the perspective of having less files. </p>
  
  <p>I've been using Razor Pages for a while and noticed that despite an advantage of a Razor Page simplicity, it is a bit complicated when it comes to custom routing, structuring folders and complex view model (page model seem to be cluttered).</p>
  
  <p>So, the questions are:</p>
  
  <ol>
  <li>If there is anything else except simplicity of a page to prefer Razor Pages over Controllers/Views - specifically I'm interested in performance of the two frameworks?</li>
  <li>Is it acceptable to combine Razor Pages and Controllers/Views at the same time?</li>
  </ol>
  
  <p>I would also appreciate if some of expirienced guys shared your thoughts (pros and cons) about using Razor Pages to better understand this framework. </p>