mxlockwood mxlockwood

Niner since 2016


  • Introducing ASP.NET Core 2.0

    It seems to me that Razor Pages are a step circling back to some sort of monolithic app. There are many good reasons for the MVC pattern. I realize the MVC pattern still exists in ASP.NET Core 2.0, but stacking it all within a single Razor Page, although flexible, optional, and a quick and dirty way of throwing something together, it is just a quick and dirty way of throwing an app. together. Doesn't it defeat the purpose of the MVC design pattern? I certainly don't believe it compliments it. Or does it?