Asp,net Inside MVC Architecture

Inside MVC Architecture

The entire ASP.NET MVC architecture is based on Microsoft .NET Framework 3.5 and in addition uses LINQ to SQL Server.
 

What is a Model?

1. MVC model is basically a C# or VB.NET class
2. A model is accessible by both controller and view
3. A model can be used to pass data from Controller to view
4. A view can use model to display data in page.

What is a View?

1. View is an ASPX page without having a code behind file
2. All page specific HTML generation and formatting can be done inside view
3. One can use Inline code (server tags ) to develop dynamic pages
4. A request to view (ASPX page) can be made only from a controller’s action method

What is a Controller?

1. Controller is basically a C# or VB.NET class which inherits system.mvc.controller
2. Controller is a heart of the entire MVC architecture
3. Inside Controller’s class action methods can be implemented which are responsible for responding to browser OR calling views.
4. Controller can access and use model class to pass data to views
5. Controller uses ViewData to pass any data to view    
   Overview:.
   

• The user interacts with the user interface in some way (for example, by pressing a mouse button).
• The controller handles the input event from the user interface, often via a registered handler or callback, and converts the event into an appropriate user action, understandable for the model.
• The controller notifies the model of the user action, possibly resulting in a change in the model's state. (For example, the controller updates the user's shopping cart.)^[4]
• A view queries the model in order to generate an appropriate user interface (for example the view lists the shopping cart's contents). The view gets its own data from the model. In some implementations, the controller may issue a general instruction to the view to render itself. In others, the view is automatically notified by the model of changes in state (Observer) that require a screen update.
• The user interface waits for further user interactions, which restarts the control flow cycle.