Top 50 Aspmvc
Top 50 Aspmvc
It supports TTD (test-driven development). We can create an application with unit test. We can
write won test case.
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.
Razor is the first major update to render HTML in MVC 3. Razor was designed specifically for view engine
syntax. Main focus of this would be to simplify and code-focused templating for HTML generation. Below
is the sample of using Razor:
@model MvcMusicStore.Models.Customer
@{ViewBag.Title = “Get Customers”;}
<div class=”cust”> <h3><em>@Model.CustomerName</em> </h3>
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.
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.
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.
11) What are Actions in MVC?
Actions are the methods in Controller class which is responsible for returning the view or json data.
Action will mainly have return type — “ActionResult” and it will be invoked from method
— “InvokeAction()” called by controller.
ASP.NET Web API supports this type routing. This is introduced in MVC5. In this type of routing, attributes
are being used to define the routes. This type of routing gives more control over classic URI Routing.
Attribute Routing can be defined at controller level or at Action level like –
[Route(“{action = TestCategoryList}”)] — Controller Level
[Route(“customers/{TestCategoryId:int:min(10)}”)] — Action Level
Just add the method — “MapMvcAttributeRoutes()” to enable attribute routing as shown below
);
JavaScript Object Notation (JSON) binding support started from MVC3 onwards via the new
JsonValueProviderFactory, which allows the action methods to accept and model-bind data in JSON
format. This is useful in Ajax scenarios like client templates and data binding that need to post data back
to the server.
15) Explain Dependency Resolution?
Dependency Resolver again has been introduced in MVC3 and it is greatly simplified the use of
dependency injection in your applications. This turn to be easier and useful for decoupling the application
components and making them easier to test and more configurable.
“BundleConfig.cs” in MVC4 is used to register the bundles by the bundling and minification system. Many
bundles are added by default including jQuery libraries like — jquery.validate, Modernizr, and default CSS
references.
Method — “RegisterRoutes()” is used for registering the routes which will be added in
“Application_Start()” method of global.asax file, which is fired when the application is loaded or started.
System.Web.Mvc
System.Web.Mvc.Ajax
System.Web.Mvc.Html
System.Web.Mvc.Async
Viewdata contains the key, value pairs as dictionary and this is derived from class
— “ViewDataDictionary“. In action method we are setting the value for viewdata and in view the value
will be fetched by typecasting.
ViewBag will take advantage of dynamic keyword which is introduced in version 4.0. But before using
ViewBag we have to keep in mind that ViewBag is slower than ViewData.
TempData is again a key, value pair as ViewData. This is derived from “TempDataDictionary” class.
TempData is used when the data is to be used in two consecutive requests, this could be between the
actions or between the controllers. This requires typecasting in view.
HTML Helpers are like controls in traditional web forms. But HTML helpers are more lightweight
compared to web controls as it does not hold viewstate and events.
HTML Helpers returns the HTML string which can be directly rendered to HTML page. Custom HTML
Helpers also can be created by overriding “HtmlHelper” class.
HTML helpers help you to render HTML controls in the view. For instance if you want to display a HTML
textbox on the view , below is the HTML helper code.
<%= Html.TextBox("FirstName") %>
For checkbox below is the HTML helper code. In this way we have HTML helper methods for every HTML
control that exists.
<%= Html.CheckBox("Yes") %>
AJAX Helpers are used to create AJAX enabled elements like as Ajax enabled forms and links which
performs the request asynchronously and these are extension methods of AJAXHelper class which exists
in namespace — System.Web.Mvc.
Confirm — This is used to specify the message which is to be displayed in confirm box.
OnBegin — Javascript method name to be given here and this will be called before the AJAX request.
OnComplete — Javascript method name to be given here and this will be called at the end of AJAX
request.
OnSuccess — Javascript method name to be given here and this will be called when AJAX request is
successful.
OnFailure — Javascript method name to be given here and this will be called when AJAX request is failed.
UpdateTargetId — Target element which is populated from the action returning HTML.
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”;
This indicates child page uses TestLayout page as it’s master 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”)
<h1>Test Content</h1>
If any child page does not have this section defined then error will be thrown so to avoid that we can
render the HTML like this –
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.
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.
Below are the methods used to render the views from action -
RedirectToRoute() — Redirect to action from the specified URL but URL in the route table has been
matched.
30) What are the sub types of ActionResult?
ActionResult is used to represent the action method result. Below are the subtypes of ActionResult –
ViewResult (View): This return type is used to return a webpage from an action method.
PartialviewResult (Partialview): This return type is used to send a part of a view which will be
rendered in another view.
RedirectResult (Redirect): This return type is used to redirect to any other controller and action
method depending on the URL.
RedirectToRouteResult (RedirectToAction, RedirectToRoute): This return type is used when we
want to redirect to any other action method.
ContentResult (Content): This return type is used to return HTTP content type like text/plain as
the result of the action.
jsonResult (json): This return type is used when we want to return a JSON message.
javascriptResult (javascript): This return type is used to return JavaScript code that will run in
browser.
FileResult (File): This return type is used to send binary output in response.
EmptyResult: This return type is used to return nothing (void) in the result.
HTTPStatusCodeResult
In 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]
// Method logic
“ActionName” attribute can be used for changing the action name. Below is the sample code snippet to
demonstrate more –
[ActionName(“TestActionNew”)]
return View();
So in the above code snippet “TestAction” is the original action name and in “ActionName” attribute,
name — “TestActionNew” is given. So the caller of this action method will use the name “TestActionNew”
to call this action.
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”;
The HelperPage.IsAjax property gets a value that indicates whether Ajax is being used during the request
of the Web page.
35) How we can call a JavaScript function on the change of a Dropdown List in MVC?
<script type=”text/javascript”>
function DrpIndexChanged() { }
</script>
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”)
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”); }
“RouteConfig.cs” holds the routing configuration for MVC. RouteConfig will be initialized on
Application_Start event registered in Global.asax.
Empty
Create
Delete
Details
Edit
List
42) Can a view be shared across multiple controllers? If Yes, How we can do that?
Yes, we can share a view across multiple controllers. We can put the view in the “Shared” folder. When
we create a new 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.
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.
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.
45) Can we add constraints to the route? If yes, explain how we can do it?
Below are the two types of extensions razor view can have –
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()
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.
Glimpse is an open source tool for debugging the routes in MVC. It is the client side debugger. Glimpse
has to be turned on by visiting to local url link -
http://localhost:portname//glimpse.axd
This is a popular and useful tool for debugging which tracks the speed details, url details etc.
In MVC, many times we would like to perform some action before or after a particular operation. For
achieving this functionality, ASP.NET MVC provides feature to add pre and post action behaviors on
controller's action methods.
Types of Filters:
Action Filters: Action filters are used to implement logic that gets executed before and after a controller
action executes.
Authorization Filters: Authorization filters are used to implement authentication and authorization for
controller actions.
Result Filters: Result filters contain logic that is executed before and after a view result is executed. For
example, you might want to modify a view result right before the view is rendered to the browser.
Exception Filters: You can use an exception filter to handle errors raised by either your controller actions
or controller action results. You can also use exception filters to log errors.
Action Filters are additional attributes that can be applied to either a controller section or the entire
controller to modify the way in which action is executed. These attributes are special .NET classes
derived from System.Attribute which can be attached to classes, methods, properties and fields.
Output Cache: This action filter caches the output of a controller action for a specified amount of time.
Handle Error: This action filter handles errors raised when a controller action executes.
Authorize: This action filter enables you to restrict access to a particular user or role.
Now we will see the code example to apply these filters on an example controller
ActionFilterDemoController. (ActionFilterDemoController is just used as an example. You can use these
filters on any of your controllers.)
Output Cache
E.g.: Specifies the return value to be cached for 10 seconds.
publicclassActionFilterDemoController: Controller {
[HttpGet]
OutputCache(Duration = 10)]
publicstringIndex() {
returnDateTime.Now.ToString("T"); }
}
13. What is the difference between Temp data, View, and View Bag?
In ASP.NET MVC there are three ways to pass/store data between the controllers and views.
ViewData
ViewBag
ViewBag is also used to pass data from the controller to the respective view.
ViewBag is a dynamic property that takes advantage of the new dynamic features in C# 4.0
It is also available for the current request only.
If redirection occurs, then its value becomes null.
Doesn’t require typecasting for complex data type.
TempData
16. Explain what is the difference between View and Partial View?
View:
It contains the layout page.
Before any view is rendered, viewstart page is rendered.
View might have markup tags like body, html, head, title, meta etc.
View is not lightweight as compare to Partial View.
Partial View:
It does not contain the layout page.
Partial view does not verify for a viewstart.cshtml.We cannot put common code for a partial view within
the viewStart.cshtml.page.
Partial view is designed specially to render within the view and just because of that it does not consist
any mark up.
We can pass a regular view to the RenderPartial method.
Once “TempData” is read in the current request it’s not available in the subsequent request. If we want
“TempData” to be read and also available in the subsequent request then after reading we need to call
“Keep” method as shown in the code below.
@TempData["MyData"];
TempData.Keep("MyData");
The more shortcut way of achieving the same is by using “Peek”. This function helps to read as well
advices MVC to maintain “TempData” for the subsequent request.
string str = TempData.Peek("MyData ").ToString();
Bundling and minification are two new techniques introduced to improve request load time. It improves
load time by reducing the number of requests to the server and reducing the size of requested assets
(such as CSS and JavaScript).
Bundling: It lets us combine multiple JavaScript (.js) files or multiple cascading style sheet (.css) files so
that they can be downloaded as a unit, rather than making individual HTTP requests.
Minification: It squeezes out whitespace and performs other types of compression to make the
downloaded files as small as possible. At runtime, the process identifies the user agent, for example IE,
Mozilla, etc. and then removes whatever is specific to Mozilla when the request comes from IE.
Action methods on controllers return JsonResult (JavaScript Object Notation result) that can be used in
an AJAX application. This class is inherited from the "ActionResult" abstract class. Here Json is provided
one argument which must be serializable. The JSON result object that serializes the specified object to
JSON format.
public JsonResult JsonResultTest() {
Calling of ViewData is :
ViewData["Name"] = " Vikash ";
In the controller you can override the “OnException” event and set the “Result” to the view name which
you want to invoke when error occurs. In the below code you can see we have set the “Result” to a view
named as “Error”.
We have also set the exception so that it can be displayed inside the view.
Exception ex = filterContext.Exception;
filterContext.ExceptionHandled = true;
ViewName = "Error",
};
}
}
To display the above error in view we can use the below code
@Model.Exception;
Dependency Resolver again has been introduced in MVC3 and it is greatly simplified the use of
dependency injection in your applications. This turn to be easier and useful for decoupling the
application components and making them easier to test and more configurable.
"BundleConfig.cs" in MVC4 is used to register the bundles by the bundling and minification system.
Many bundles are added by default including jQuery libraries like - jquery.validate, Modernizr, and
default CSS references.