Asp MVC Interview Question and answer

Asp MVC Interview Question and answer 1) What is MVC? Ans . MVC stands for model-view-controller. it is a software design pattern ... thumbnail 1 summary

04:08

Asp MVC Interview Question and answer

1) What is MVC?
Ans.
MVC stands for model-view-controller. it is a software design pattern which was introduced in 1970s. MVC pattern forces a sepration of concerns, it means domain model and controller logic are decoupled from user interface.

2)Explain MVC Pattern?
Ans.

Model :-
It is the part of the application that handles the logic for the application data. Often model objects retrieve data (and store data) from a database.

View :-
It is the parts of the application that handles the display of the data. Most often the views are created from the model data.

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.

3)Difference between ASP.NET Webform and ASP.NET MVC ?

ASP.NET Webform :-

1)ASP.NET Web Form follows a traditional event driven development model.

2)ASP.NET Web Form has file-based URLs means file name exist in the URLs must have its physically existence.

3)ASP.NET Web Form has server controls.

4)ASP.NET Web Form follows WebForm Syntax

5)ASP.NET Web Form has Master Pages for consistent look and feels.

6)ASP.NET Web Form has User Controls for code re-usability.

7)ASP.NET Web Form is not Open Source.

ASP.NET MVC :-

1)ASP.NET MVC is a lightweight and follow MVC pattern based development model.

2)ASP.NET MVC has route-based URLs means URLs are divided into controllers and actions and moreover it is based on controller not on physical file.

3)ASP.NET MVC has html helpers.

4)ASP.NET MVC follow customizable syntax

5)ASP.NET MVC has Layouts for consistent look and feels.

6)ASP.NET MVC has Partial Views for code re-usability

7)ASP.NET Web MVC is an Open Source.

These component roles are used for various purposes like handling end user interaction, manipulating the model, and ultimately choosing a view to render to display UI.
- See more at: http://www.dotnetfunda.com/interviews/cat/131/aspnet-mvc#sthash.AgQCUC0e.dpuf

These component roles are used for various purposes like handling end user interaction, manipulating the model, and ultimately choosing a view to render to display UI. - See more at: http://www.dotnetfunda.com/interviews/cat/131/aspnet-mvc#sthash.AgQCUC0e.dpuf