First, choosing between regular views and Razor Pages is a decision that should be made upfront—they're just too different. Having controllers and views may be more appealing to people who have worked with MVC before, and I'd say it can result in better coupling and organization, but Razor Pages is just so easy to use—no server-side code and no recompilation (if the page model is not used)are required.
Keep on using partial views and view layouts as they are a good mechanism to improve reusability.
The same security concerns apply to Razor Pages as they do to controller actions. It might be better to prefer conventions over attributes, as we have a central location where the security information is stored.
In this chapter, we were introduced to the new Razor Pages feature of ASP.NET Core 2, which, although different from the ordinary views, shares quite a bit of functionality. It can be used for simpler solutions, without...
