You do not need to create Custom View Engine for most projects. The reason for using Custom View Engine is to change the default views location at run-time. The MVC Framework has two built-in view engines – Razor and WebForms. View engines implement IViewEngine interface:
Filters inject extra logic into MVC Framework request processing. They provide a simple and elegant way to implement cross-cutting concerns. This term refers to functionality that is used all over an application and doesn’t fit neatly into any one place, where it would break the separation of concerns pattern. Classic examples of cross-cutting concerns are […]
The repository and unit of work patterns are intended to create an abstraction layer between the data access layer and the business logic layer of an application. Implementing these patterns can help insulate your application from changes in the data store and can facilitate automated unit testing or test-driven development (TDD).
On the client: Cookie On the server: Cache (make sure to use user specific key to avoid collisions) Some back-end storage (such as a database) ASP.NET Session ViewData – dictionary that accessible by string keys ViewBag – ViewData wrapper that allows to create dynamic properties. In addition we can use TempData that is basically dictionary that […]