Model View Controller-Introduction-Overview.pptx

MARIO B. CADAY
Instructor I
Introduction to MVC

Introduction to MVC
 Software design pattern for developing web applications
 Software architecture pattern which separates the representation of information from the
users interaction with it
 Here M stands for Model, V stands for View and C stands for controller
 ASP.NET MVC helps to develop powerful and pattern-based dynamic websites that enables
a clean separation of concerns and also gives full control on a mark-up
 Also it includes many features that help to develop a sophisticated and modern web
application
https://www.ifourtechnolab.com/

MVC vs WEB FORMS
MVC Web Forms
Easier to Manage Complexity Preservers State over HTTP
Does not use view state or server based forms Page Controller Pattern
Rich Routing Structure View state or server based forms
Support for Test-Driven Development Works well for small teams
Supports Large Teams Well Development is less complex

Architecture of MVC
 A Model View Controller pattern is made up of the following three parts:
 Model
 View
 Controller
•A markup language is a set of markup tags

Architecture of MVC (Cont.)
 Model:
 Responsible for managing the data of the application
 It responds to the request from the view and it also responds to instructions from the controller
to update itself
 Lowest level pattern which is responsible for maintaining data
 Represents the application core (for instance a list of database records)
 Also called the domain layer

 View:
 The View displays the data (the database records)
 A view requests information from the model, that it needs to generate an output representation
 Presents data in a particular format like JSP, ASP, PHP
 MVC is often seen in web applications, where the view is the HTML page

 Controller:
 It is the part of the application that handles user interaction
 Typically controllers read data from a view, control user input, and send input data to the model
 It handles the input, typically user actions and may invoke changes on the model and view

Routing
 A route is a URL pattern that is mapped to a handler
 The handler can be a physical file, such as an .aspx file in a Web Forms application. A
handler can also be a class that processes the request, such as a controller in an MVC
application
 At runtime, Routing engine use the Route table for matching the incoming request's URL
pattern against the URL patterns defined in the Route table
 Register one or more URL patterns to the Route table at Application_Start event
 When the routing engine finds a match in the route table for the incoming request's URL,
it forwards the request to the appropriate controller and action
 If there is no match in the route table for the incoming request's URL, it returns a 404
HTTP status code

How it works?

How to define route?
public static void RegisterRoutes(RouteCollection routes)
{
routes.MapRoute(
"Default", //Route name
"{controller}/{action}/{id}", //URL with parameters
new { controller = "Home", action = "Index", id = UrlParameter.Optional } //Default parameters
);
}
protected void Application_Start()
{
RegisterRoutes(RouteTable.Routes);
//To:DO
}

Bundling
It is a simple logical group of files that could be referenced by unique name and being
loaded with one HTTP requestor
Bundling and minification reduces the number of HTTP Requests and payload size resulting
in faster and better performing ASP.NET MVC Websites

How to define bundling?
public static void RegisterBundles(BundleCollection bundles)
{
bundles.Add(new ScriptBundle("~/bundles/jqueryval").Include(
"~/Scripts/jquery.unobtrusive*",
“~/Scripts/my_custom_js.js”,
….....List of Js..............));
}
protected void Application_Start()
{
BundleConfig.RegisterBundles(BundleTable.Bundles)
}

Filter
 ASP.NET MVC Filter is a custom class where you can write custom logic to execute before or after
an action method executes
 Filters can be applied to an action method or controller in a declarative or programmatic way
 MVC provides different types of filters
Filter Type Description Built-in Filter Interface
Authorization
filters
Performs authentication and authorizes before executing action
method
[Authorize]
[RequireHttps]
IAuthorizationFilter
Action filters Performs some operation before and after an action method
executes
IActionFilter
Result filters Performs some operation before or after the execution of view result [OutputCache] IResultFilter
Exception filters Performs some operation if there is an unhandled exception thrown
during the execution of the ASP.NET MVC pipeline
[HandleError] IExceptionFilter

Filter
 Filters can be applied at three levels :
 Global Level: Global filters will be applied to all the controller and action methods of an application
// MvcApplication class contains in Global.asax.cs file
public class MvcApplication : System.Web.HttpApplication
{ protected void Application_Start()
{ FilterConfig.RegisterGlobalFilters(GlobalFilters.Filters); }
}
// FilterConfig.cs located in App_Start folder
public class FilterConfig
{ public static void RegisterGlobalFilters(GlobalFilterCollection filters)
{ filters.Add(new HandleErrorAttribute()); }
}

Filter
• Controller Level: Filters can also be applied to the controller class. So, filters will be
applicable to all the action method of Controller class if it is applied to a controller class
[HandleError]
public class HomeController : Controller
{
public ActionResult Index()
{
return View();
}
}

Filter
 Action method level: Apply filters to an individual action method. So, filter will be
applicable to that particular action method only.
public class HomeController : Controller
{ [HandleError]
public ActionResult Index()
{ return View(); }
}
 Filters run in the following order.
 Authorization filters, Action filters, Response filters, Exception filters

Model View Controller-Introduction-Overview.pptx

Recommended

More Related Content

Similar to Model View Controller-Introduction-Overview.pptx (20)

More from MarioCaday2 (11)

Recently uploaded (20)

Model View Controller-Introduction-Overview.pptx

Editor's Notes