Description CORS (Cross-Origin-Resource-Sharing) is a mechanism that allows a web application running at one origin toRead more
Description ViewComponents are powerfull solutions that allows the developer to keep his code clean and reusable.Read more
Description In the MVC lifecyle ActionFilter execute just before the action is invoked. These filters areRead more
Usage
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 |
public class AuthenticateController : Controller { private readonly IActionCommandSystemService _ActionCommandSystemService; public AuthenticateController(IActionCommandSystemService actionCommandSystemService) { this._ActionCommandSystemService = actionCommandSystemService; } public IActionResult Login() { //AuthenticateLoginGetCommand - our command class //ViewResult - the result type return this._ActionCommandSystemService .Execute<AuthenticateLoginGetCommand, ViewResult>(this); } } //Our Command Class public class AuthenticateLoginGetCommand : ActionCommandController { public override ViewResult Execute() { //more logic here //this.ControllerContext = using the same context as the invoker; //this.HttpContext = using the same context as the ; //returns the View with the name Login - same as the invoker return View(); } } |
Description Controllers may tend to be overcrowded when developing large scale applications. Controllers oftenRead more
Description CORS (Cross-Origin-Resource-Sharing) is a mechanism that allows a web application running at one origin to access the resources from a server running at a different origin. The same-origin policy is a very restrictive measure because it only allows applications on the same origin as the server to access it’s resources but it also bringsRead more
Description ViewComponents are powerfull solutions that allows the developer to keep his code clean and reusable. Unfortunatelly it has the same functionality as all the Views and for the current version (.NET Core 2.2) there is no proper support of defining scripts and style tag in a view component but to render them in theRead more
Description In the MVC lifecyle ActionFilter execute just before the action is invoked. These filters are provided with the action context from which we can access and manipulate the controller context. In this example I will show how to access a service in an action filter, and add data in the ViewData that can beRead more
Usage
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 |
public class AuthenticateController : Controller { private readonly IActionCommandSystemService _ActionCommandSystemService; public AuthenticateController(IActionCommandSystemService actionCommandSystemService) { this._ActionCommandSystemService = actionCommandSystemService; } public IActionResult Login() { //AuthenticateLoginGetCommand - our command class //ViewResult - the result type return this._ActionCommandSystemService .Execute<AuthenticateLoginGetCommand, ViewResult>(this); } } //Our Command Class public class AuthenticateLoginGetCommand : ActionCommandController { public override ViewResult Execute() { //more logic here //this.ControllerContext = using the same context as the invoker; //this.HttpContext = using the same context as the ; //returns the View with the name Login - same as the invoker return View(); } } |
Description Controllers may tend to be overcrowded when developing large scale applications. Controllers often become the space of multiple responsibilities and complex logic. A good approach would be to separate this logic into separate containers and access them from the controller. This is exactly what MediatR does (see Mediator Design Pattern). MediatR providesRead more
