Explore topic-wise InterviewSolutions in .

Below is the code snippet to return string from action method :

public ActionResult TestAction() {return JSON(new { prop1 = "Test1", prop2 = "Test2" });}

Below is the code snippet to return string from action method :

public ActionResult TestAction() {return Content("Hello Test !!");}

Yes. We can use the razor code in javascript in cshtml by using <text> element.

< script type="text/javascript">foreach (var item in Model) {< text >//javascript goes here which uses the server values< text >}< script>

No. We can't set unlimited length for property maxJsonLength. Default value is - 102400 and maximum value what we can set would be : 2147483644.

• Display Templates : These are model centric. Meaning it depends on the properties of the view model used. It uses convention that will only display like divs or labels.
• Edit Templates : These are also model centric but will have editable controls like Textboxes.
• Partial View : These are view centric. These will differ from templates by the way they render the properties (Id's) Eg : CategoryViewModel has Product class property then it will be rendered as Model.Product.ProductName but in case of templates if we CategoryViewModel has List then Html.DisplayFor(m => m.Products) works and it renders the template for each item of this list.

Below is the scenario and the solution to solve multiple submit buttons issue.Scenario :

using (Html.BeginForm("MyTestAction","MyTestController"){    <input type="submit" value="MySave" />    <input type="submit" value="MyEdit" />}

Public ActionResult MyTestAction(string submit) //submit will have value either "MySave" or "MyEdit"{    // Write code here}

We can use dataannotations for validation in ASP.Net MVC. If we want to use validation during runtime using Jquery then we can use Jquery plugins for validation.Eg: If validation is to be done on customer name textbox then we can do as :

$('#CustomerName').rules("add", {required: true,minlength: 2,messages: {required: "Please enter name",minlength: "Minimum length is 2"}});

REST is an architectural style which uses HTTP protocol methods like GET, POST, PUT, and DELETE to access the data. ASP.Net MVC works in this style. In ASP.Net MVC 4 there is a support for Web API which uses to build the service using HTTP verbs.

Below are the tools used for unit testing :

• NUnit
• xUnit.NET
• Ninject 2
• Moq

TDD is a methodology which says, write your tests first before you write your code. In TDD, tests drive your application design and development cycles. You do not do the check-in of your code into source control until all of your unit tests pass.

Below are the advantages of DI :

• Reduces class coupling
• Increases code reusing
• Improves code maintainability
• Improves application testing

it's a design pattern and is used for developing loosely couple code. This is greatly used in the software projects. This will reduce the coding in case of changes on project design so this is vastly used.

"ChildActionOnly" attribute is decorated over action methods to indicate that action method is a child action. Below is the code snippet used to denote the child action :

[ChildActionOnly]public ActionResult MenuBar(){//Logic herereturn PartialView();}

To create reusable widgets child actions are used and this will be embedded into the parent views. In ASP.Net MVC Partial views are used to have reusability in the application. Child action mainly returns the partial views.

When we have created an area make sure this will be registered in "Application_Start" event in Global.asax. Below is the code snippet where area registration is done :

protected void Application_Start(){AreaRegistration.RegisterAllAreas();}

Similar to Keep method we have one more method called "Peek" which is used for the same purpose. This method used to read data in Tempdata and it maintains the data for subsequent request.

string A4str = TempData.Peek("TT").ToString();

As explained above in case data in Tempdata has been read in current request only then "Keep" method has been used to make it available for the subsequent request.

TempData["TestData"];TempData.Keep("TestData");

If Tempdata is assigned in the current request then it will be available for the current request and the subsequent request and it depends whether data in TempData read or not. If data in Tempdata is read then it would not be available for the subsequent requests.

Exception Handling is made simple in ASP.Net MVC and it can be done by just overriding "OnException" and set the result property of the filtercontext object (as shown below) to the view detail, which is to be returned in case of exception.

protected overrides void OnException(ExceptionContext filterContext)    {    }

For Model Binding we will use class called : "ModelBinders", which gives access to all the model binders in an application. We can create a custom model binders by inheriting "IModelBinder".

In Web.Config there are tags called : "ClientValidationEnabled" and "UnobtrusiveJavaScriptEnabled". We can set the client side validation just by setting these two tags "true", then this setting will be applied at the application level.

< add key="ClientValidationEnabled" value="true" />< add key="UnobtrusiveJavaScriptEnabled" value="true" />

Whenever validation fails it will be tracked in ModelState. By using property : IsValid it can be determined. In Server code, check like this :

if(ModelState.IsValid){     // No Validation Errors}

This can be done in following way :Use class : "HttpRequestBase" and use the method : "HttpMethod" to determine the action request type.

Below are some action filters used :

• Authentication
• Authorization
• HandleError
• OutputCache

Action Filters allow us to execute the code before or after action has been executed. This can be done by decorating the action methods of controls with ASP.Net MVC attributes.

Glimpse is an open source tool for debugging the routes in ASP.Net MVC. It is the client side debugger. Glimpse has to be turned on by visiting to local url link -http://localhost:portname//glimpse.axdThis is a popular and useful tool for debugging which tracks the speed details, url details etc.

No. We cannot add the test cases in Visual Studio Express edition it can be added only in Professional and Ultimate versions of Visual Studio.

Below is the sample code snippet to add css to razor views :< link rel="StyleSheet" href="/Href(~Content/Site.css")" type="text/css"/>

PartialView is similar to UserControls in traditional web forms. For re-usability purpose partial views are used. Since it's been shared with multiple views these are kept in shared folder. Partial Views can be rendered in following ways :

• Html.Partial()
• Html.RenderPartial()

Below are the two types of extensions razor view can have :

• .cshtml : In C# programming language this extension will be used.
• .vbhtml - In VB programming language this extension will be used.

Yes we can add constraints to route in following ways :

• Using Regular Expressions
• Using object which implements interface - IRouteConstraint.

Using this default route - {resource}.axd/{*pathInfo}, we can prevent the requests for the web resources files like - WebResource.axd or ScriptResource.axd from passing to a controller.

• Name - This is the name of the route.
• URL Pattern : Placeholders will be given to match the request URL pattern.
• Defaults :When loading the application which controller, action to be loaded along with the parameter.

Yes we can share a view across multiple controllers. We can put the view in the "Shared" folder. When we create a new ASP.Net MVC Project we can see the Layout page will be added in the shared folder, which is because it is used by multiple child pages.

Below are the types of scaffoldings :

• Empty
• Create
• Delete
• Details
• Edit
• List

Scaffolding in ASP.NET ASP.Net MVC is used to generate the Controllers,Model and Views for create, read, update, and delete (CRUD) functionality in an application. The scaffolding will be knowing the naming conventions used for models and controllers and views.

"RouteConfig.cs" holds the routing configuration for ASP.Net MVC. RouteConfig will be initialized on Application_Start event registered in Global.asax.

Result of the method : "RenderPartial" is directly written to the HTML response. This method does not return anything (void). This method also does not depend on action methods. RenderPartial() method calls "Write()" internally and we have to make sure that "RenderPartial" method is enclosed in the bracket. Below is the sample code snippet :{Html.RenderPartial("TestPartialView"); }

This method is used to render the specified partial view as an HTML string. This method does not depend on any action methods. We can use this like below :Html.Partial("TestPartialView")

Create a JavaScript method:

function DrpIndexChanged() { }

< %:Html.DropDownListFor(x => x.SelectedProduct, new SelectList(Model.Customers, "Value", "Text"), "Please Select a Customer", new { id = "ddlCustomers", onchange=" DrpIndexChanged ()" })%>

The HelperPage.IsAjax property gets a value that indicates whether Ajax is being used during the request of the Web page.

Unlike code expressions that are evaluated and sent to the response, it is the blocks of code that are executed. This is useful for declaring variables which we may be required to be used later.

{ int x = 123; string y = "aa"; }

"ActionName" attribute can be used for changing the action name. Below is the sample code snippet to demonstrate more :

[ActionName("TestActionNew")]public ActionResult TestAction()    {        return View();    }

In ASP.Net MVC all public methods have been treated as Actions. So if you are creating a method and if you do not want to use it as an action method then the method has to be decorated with "NonAction" attribute as shown below :

[NonAction]public void TestMethod(){// Method logic}

ActionResult is used to represent the action method result. Below are the subtypes of ActionResult :

• ViewResult
• PartialViewResult
• RedirectToRouteResult
• RedirectResult
• JavascriptResult
• JSONResult
• FileResult
• HTTPStatusCodeResult

Below are the methods used to render the views from action -

• View() : To return the view from action.
• PartialView() : To return the partial view from action.
• RedirectToAction() : To Redirect to different action which can be in same controller or in different controller.
• Redirect() : Similar to "Response.Redirect()" in webforms, used to redirect to specified URL.
• RedirectToRoute() : Redirect to action from the specified URL but URL in the route table has been matched.

This page is used to make sure common layout page will be used for multiple views. Code written in this file will be executed first when application is being loaded.

RenderBody is like ContentPlaceHolder in web forms. This will exist in layout page and it will render the child pages/views. Layout page will have only one RenderBody() method. RenderPage also exists in Layout page and multiple RenderPage() can be there in Layout page.

Section are the part of HTML which is to be rendered in layout page. In Layout page we will use the below syntax for rendering the HTML :

RenderSection("TestSection")

section TestSection{<h1>Test Content<h1>}

RenderSection("TestSection", required: false)

Layout pages are similar to master pages in traditional web forms. This is used to set the common look across multiple pages. In each child page we can find : /p>

{Layout = "~/Views/Shared/TestLayout1.cshtml";}