View layouts are a must-have; try to avoid nested (or too nested) view layouts, as it may be difficult to understand the final result. Partial views are also very handy, but make sure you use them to avoid repeating code.
We should also avoid having code in views—for example, by specifying custom view classes; use filters for that purpose. We saw that we should consider the localization needs of your app upfront; it's very difficult and error-prone to refactor an existing app that does not use localization to introduce it.
Then, next, we saw that for security, you can use code or tag helpers to keep sensitive parts of your views secure.
Stick to the conventions in terms of folder names and the like. This will make things easier for everyone, currently and in the future, in your team.
We learned that _ViewImports.cshtml and _ViewStart.cshtml are your friends—use them for common code that you want to be applied to all your...
