Explore topic-wise InterviewSolutions in .

ROUTING is a pattern matching mechanism of INCOMING REQUESTS to the URL patterns which are REGISTERED in route table. Class – “UrlRoutingModule” is used for the same process.

Routing is a pattern matching mechanism of incoming requests to the URL patterns which are registered in route table. Class – “UrlRoutingModule” is used for the same process.

ViewModel is a plain class with PROPERTIES, which is USED to bind it to strongly TYPED view. ViewModel can have the validation RULES defined for its properties using data ANNOTATIONS.

ViewModel is a plain class with properties, which is used to bind it to strongly typed view. ViewModel can have the validation rules defined for its properties using data annotations.

This is a general term that conveys a general philosophy, similar to the term REST (Representational STATE Transfer). UNOBTRUSIVE JavaScript doesn't INTERMIX JavaScript code in your page markup.

Eg : Instead of using events like onclick and onsubmit, the unobtrusive JavaScript ATTACHES to elements by their ID or class based on the HTML5 data- attributes.

This is a general term that conveys a general philosophy, similar to the term REST (Representational State Transfer). Unobtrusive JavaScript doesn't intermix JavaScript code in your page markup.

Eg : Instead of using events like onclick and onsubmit, the unobtrusive JavaScript attaches to elements by their ID or class based on the HTML5 data- attributes.

It’s is the process of breaking the PROGRAM into various DISTINCT features which OVERLAPS in functionality as little as possible. MVC pattern CONCERNS on separating the content from presentation and data-processing from content.

It’s is the process of breaking the program into various distinct features which overlaps in functionality as little as possible. MVC pattern concerns on separating the content from presentation and data-processing from content.

• Provides a clean separation of concerns among UI (Presentation layer), model (Transfer objects/Domain Objects/Entities) and Business Logic (Controller).
• EASY to UNIT Test.
• IMPROVED reusability of model and views. We can have MULTIPLE views which can point to the same model and vice versa.
• Improved STRUCTURING of the code.

Below are the PROCESSED followed in the sequence:

• App INITIALIZATION
• Routing
• Instantiate and execute controller
• LOCATE and invoke controller action
• Instantiate and render VIEW.

Below are the processed followed in the sequence:

FOLLOWING are features added NEWLY:

• Mobile templates
• Added ASP.NET Web API template for creating REST based services.
• ASYNCHRONOUS controller TASK support.
• Bundling the java scripts.
• Segregating the configs for MVC routing, Web API, Bundle etc.

Following are features added newly:

• MODEL – It’s a business entity and it is used to represent the application DATA.
• Controller – REQUEST sent by the user always scatters through controller and it’s responsibility is to REDIRECT to the SPECIFIC view using View() method.
• View – It’s the presentation layer of MVC.