Explore topic-wise InterviewSolutions in Current Affairs.

YES, MVC 4 is supporting WINDOWS AZURE SDK VERSION 1.6 or higher.

Yes, MVC 4 is supporting Windows Azure SDK version 1.6 or higher.

There is major difference is on implementation mechanism between ASP.NET MVC 3 and ASP.NET MVC 4.

In ASP.NET MVC 3, to implement async controller or methods we need to derive controller from AsyncController rather than from normal plain Controller class. We need to CREATE 2 action methods rather than one. First with suffix ‘Async’ KEYWORD & second with ‘Completed’ suffix.

In ASP.NET MVC 4 you need not to DECLARE 2 action method. One can SERVE the purpouse. MVC 4 using .Net Framework 4.5 support for asynchronous communication.

There is major difference is on implementation mechanism between ASP.NET MVC 3 and ASP.NET MVC 4.

In ASP.NET MVC 3, to implement async controller or methods we need to derive controller from AsyncController rather than from normal plain Controller class. We need to create 2 action methods rather than one. First with suffix ‘Async’ keyword & second with ‘Completed’ suffix.

In ASP.NET MVC 4 you need not to declare 2 action method. One can serve the purpouse. MVC 4 using .Net Framework 4.5 support for asynchronous communication.

BUNDLING & Minification reduces number of HTTP requests. Bundling & Minification COMBINES individual files into SINGLE. Bundled file for CSS & scripts and then it REDUCE’s overall size by minifying the contents of the bundle.

Bundling & Minification reduces number of HTTP requests. Bundling & Minification combines individual files into single. Bundled file for CSS & scripts and then it reduce’s overall size by minifying the contents of the bundle.

ROUTING changes: ASP.NET Web API uses same convention for config mapping that ASP.NET MVC provides.

MODEL Binding & Validation: ASP.NET Web API uses same model binding functionality, but HTTP specific context related operations only.

FILTERS: The ASP.NET Web API uses most of built-in filters from MVC.

Unit Testing: Now Unit testing based on MVC, strongly unit testable.

Routing changes: ASP.NET Web API uses same convention for config mapping that ASP.NET MVC provides.

Model Binding & Validation: ASP.NET Web API uses same model binding functionality, but HTTP specific context related operations only.

Filters: The ASP.NET Web API uses most of built-in filters from MVC.

Unit Testing: Now Unit testing based on MVC, strongly unit testable.

View can be changed automatically based on browser(For mobile and DESKTOP browser’s)

Display Modes is newly ADDED feature in ASP.NET MVC 4. VIEWS SELECTED automatically by application depending on the browser. Example: If a desktop browser requests LOGIN page of an application it will return ViewsAccountLogin.cshtml view & if a mobile browser requests home page it will return ViewsAccountLogin.mobile.cshtml view.

View can be changed automatically based on browser(For mobile and desktop browser’s)

Display Modes is newly added feature in ASP.NET MVC 4. Views selected automatically by application depending on the browser. Example: If a desktop browser requests login page of an application it will return ViewsAccountLogin.cshtml view & if a mobile browser requests home page it will return ViewsAccountLogin.mobile.cshtml view.

SMART Phones & tablets touch got smart by using NEW jQuery.Mobile.MVC NuGet pacage.

The mobile project template touch OPTIMIZED UI by using jQuery.Mobile.MVC NuGet PACKAGE for tablets and smart phones.

Smart Phones & tablets touch got smart by using new jQuery.Mobile.MVC NuGet pacage.

The mobile project template touch optimized UI by using jQuery.Mobile.MVC NuGet Package for tablets and smart phones.

• Adaptive rendering for Nice LOOK & FEEL
• Modern Looking for Mobile & Desktop browser

The NEW enhanced default project template came up with modern looking. Along with some COSMETIC enhancements, it also EMPLOYS new adaptive rendering to look nice in both desktop and mobile browsers without need of any kind of additional customization.

The new enhanced default project template came up with modern looking. Along with some cosmetic enhancements, it also employs new adaptive rendering to look nice in both desktop and mobile browsers without need of any kind of additional customization.

YES, we can still develop the RESTful services with WCF, but there are two MAIN reasons that prompt users to use Web API instead of RESTful services.

ASP.NET Web API is included in ASP.NET MVC which obviously increases TDD (Test Data Driven) approach in the development of RESTful services.

For developing RESTful services in WCF you still NEEDS lot of CONFIG settings, URI templates, contract’s & ENDPOINTS which developing RESTful services using web API is simple.

Yes, we can still develop the RESTful services with WCF, but there are two main reasons that prompt users to use Web API instead of RESTful services.

ASP.NET Web API is included in ASP.NET MVC which obviously increases TDD (Test Data Driven) approach in the development of RESTful services.

For developing RESTful services in WCF you still needs lot of config settings, URI templates, contract’s & endpoints which developing RESTful services using web API is simple.

• Web API is a NEW framework for consuming & building HTTP Services.
• Web API supports wide range of clients including different BROWSERS and mobile DEVICES.
• It is very good PLATFORM for developing RESTful services since it talk’s about HTTP.

• Easy Mobile web applications (ASP.NET MVC 4 complete focus on Mobile application development)
• Full HTML5 support
• ASP.NET MVC web application with CLOUD support
• Working with different mobile and desktop web browsers
• DESCRIPTION.
• The main objective of ASP.NET MVC 4 is making to develop mobile web applications easily.Other than mobile web applications It’s focus is also on better HTML5 support and making ASP.NET MVC web application cloud READY.
• By USING new features of ASP.NET MVC 4 you can develop web applications that can work WELL across different desktop web browsers and mobile devices.