MVC Fundamentals


A .  3 Loosely Coupled main components of An MVC Application

  • Input Logic ---------- belongs to ---------- CONTROLLER.
  • UI Logic -------------- belongs to ---------- VEIW.
  • Business Logic------- belongs to ---------- MODEL.
     
B.     Testing individual loosely Coupled components are Easier.

C.      MVC does not use VEIW-STATE or SERVER-BASED forms, thus making developers to have full control over the     Application Behavior.

D.     MVC is good for applications which need high Degree of control over the Application Behavior.

E.      ASP.NET uses “Page Controller” pattern that adds functionality to individual pages.

F.       Managing State Information is easier for ASP.NET.

G.     ASP.NET enables rapid application development.

H.     The components of ASP.NET (like the page class, controls, etc. ) are tightly integrated and usually requires less code than MVC.

I.        Components of MVC can be easily replaced / customized. You can plug-in your own view Engine, URL-Routing Policy, action-method parameter serialization and other components.

J.        MVC supports DI (Dependency-Injection) and Inversion-of-control (IOC).
  • DI ----- Enables to inject objects into a class, instead of relying on a class to create the object itself.
  • IOC --- Specifies that if an object requires another object, the first object should get the other from an outside source such as Configuration file, which makes testing easier.   
  •             
  •                                                                                Author : Ritam Atarthy.

Comments

Post a Comment

Popular posts from this blog

C# Constructor

C# Constructor and its Types – A Detailed Look Definition: In simple terms, Constructor is a special kind of method with class name as method name and gets executed when its (class) object is created. This article will give you a detailed explanation on C# constructors and its types. Now, when we look at the above definition in a broader sense, a constructor is a class method that gets automatically executed whenever class’s object is created or whenever class is initialized.   Consider following bit of code: public class MsDotNetHeaven     {         public MsDotNetHeaven()          {               //A default Constructor          }       //Class members     } In the above snippet, the method MsDotNetHeaven() is called the constructor of class MsDotNetHeaven, also called default constructor. Behind the scenes What happened behind the scenes : whenever you try to create an object of class or initialize a class, then the default constructor will be automatically i
Read more

Hiding vs Overriding

As most of you know hiding and overriding are two main features based upon inheritance, which is one of the pillars of the OOP. Using these we can redefine a member of the base class in a derived class. But what are the differences. Let me clear this with a simple example. Start a new web application project with a default web form named "WebForm1" using visual studio. Add 2 class to this project with names "BaseClass" and "DerivedClass". The "DerivedClass" should be a subclass of "BaseClass" (i.e. should define like DerivedClass: BaseClass). Define the following functions in the base class named "BaseClass".  Notice the keyword "virtual".   public   virtual   string  FunctionToOverride() {            return  "This is from base class FunctionToOverride"; } public   string  FunctionToHide() {            return  "This is from base class FunctionToHide"; } Now define th
Read more