To know best HP laptop Price....
http://www.pritscedealsindia.com/laptop/hp-laptop-series-in-india.php
http://www.pritscedealsindia.com/laptop/hp-laptop-series-in-india.php



using System.Web; using System.Web.Mvc; namespace MvcMovie.Controllers { public class HelloWorldController : Controller { // // GET: /HelloWorld/ public string Index() { return "This is my <b>default</b> action..."; } // // GET: /HelloWorld/Welcome/ public string Welcome() { return "This is the Welcome action method..."; } } }
HelloWorldController and
the first method is named Index.
Let’s invoke it from a browser. Run the application (press F5 or Ctrl+F5). In the
browser, append "HelloWorld" to the path in the address bar. (For example,
in the illustration below, it's http://localhost:1234/HelloWorld.)
The
page in the browser will look like the following screenshot. In the
method above, the code returned a string directly. You told the system
to just return some HTML, and it did!
/[Controller]/[ActionName]/[Parameters]public static void RegisterRoutes(RouteCollection routes) { routes.IgnoreRoute("{resource}.axd/{*pathInfo}"); routes.MapRoute( name: "Default", url: "{controller}/{action}/{id}", defaults: new { controller = "Home", action = "Index", id = UrlParameter.Optional } ); }
HelloWorldController class.
The second part of the URL determines the action method on the class to execute.
So /HelloWorld/Index would
cause the Index method of the HelloWorldController class to execute. Notice that we only had to browse to /HelloWorld and
the Index method
was used by default. This is because a method named Index is
the default method that will be called on a controller if one is not
explicitly specified. The third part of the URL segment (
Parameters) is for route data. We'll see route data later on in this
tutorial.Welcome method
runs and returns the string "This is the Welcome action method...". The
default MVC mapping is /[Controller]/[ActionName]/[Parameters].
For this URL, the controller is HelloWorld and Welcome is
the action method. You haven't used the [Parameters] part
of the URL yet.Welcome method
to include two parameters as shown below. Note that the code uses the C# optional-parameter feature to indicate that the
numTimes parameter should default to 1 if no value is passed for that parameter.public string Welcome(string name, int numTimes = 1) { return HttpUtility.HtmlEncode("Hello " + name + ", NumTimes is: " + numTimes); }
name and numtimes in
the URL. The
ASP.NET MVC model binding system automatically maps the named parameters from
the query string in the address bar to parameters in your method.
Parameters) is not used, the name and numTimes
parameters are passed as query strings.
The ? (question mark) in the above URL is a separator, and the query strings
follow. The & character separates query strings.public string Welcome(string name, int ID = 1) { return HttpUtility.HtmlEncode("Hello " + name + ", ID: " + ID); }
ID. The Welcome action method
cpntains a parameter
(ID) that matched the URL specification in the RegisterRoutes
method.public static void RegisterRoutes(RouteCollection routes) { routes.IgnoreRoute("{resource}.axd/{*pathInfo}"); routes.MapRoute( name: "Default", url: "{controller}/{action}/{id}", defaults: new { controller = "Home", action = "Index", id = UrlParameter.Optional } ); }In ASP.NET MVC applications, it's more typical to pass in parameters as route data (like we did with ID above) than passing them as query strings. You could also add a route to pass both the
name and numtimes in
parameters as route data in the URL. In the App_Start\RouteConfig.cs
file, add the "Hello" route:public class RouteConfig { public static void RegisterRoutes(RouteCollection routes) { routes.IgnoreRoute("{resource}.axd/{*pathInfo}"); routes.MapRoute( name: "Default", url: "{controller}/{action}/{id}", defaults: new { controller = "Home", action = "Index", id = UrlParameter.Optional } ); routes.MapRoute( name: "Hello", url: "{controller}/{action}/{name}/{id}" ); } }Run the application and browse to
/localhost:XXX/HelloWorld/Welcome/Scott/3.
Comments (9) RSS Feed