Shulou(Shulou.com)06/02 Report--

In this issue, the editor will bring you an example analysis of the mixed use of ASP.NET forms and ASP.NET MVC in the same application. The article is rich in content and analyzes and narrates it from a professional point of view. I hope you can get something after reading this article.

Not all ASP.NET MVC Web applications need to be created from scratch, and you may want to port existing ASP.NET applications to ASP.NET MVC. Is it possible to use both ASP.NE forms and ASP.NET MVC in the same application? The answer is-absolutely.

Using both ASP.NE forms and ASP.NET MVC in the same application is not only feasible, but also quite easy, because ASP.NET MVC is a framework built on ASP.NET. In fact, they have only one key difference: ASP.NET is under the System.Web namespace, while ASP.NET MVC is under the System.Web, System.Web.Routing, System.Web.Abstractions, and System.Web.Mvc namespaces, which means that adding references to these libraries (assemblies) to existing ASP.NET applications is the beginning of a combination of these two technologies.

Another advantage that ASP.NET MVC builds on ASP.NET is that application data can be easily shared between the two technologies. For example, Session is a state object that can be used in both technologies, which allows data to be shared efficiently through Session state.

An ASP.NET forms application can become an ASP.NET MVC application by performing the following steps.

1. In an existing ASP.NET application, add references to the following libraries: System.Web.Routing.dll, System.Web.Abstractions.dll, andSystem.Web.Mvc.dll

two。 Add a Controllers,Views,Views/Shared folder to an existing ASP.NET application

3. Modify the web.config file as follows (note that you modify the existing web.config of the ASP.NET application, not overwrite it):

4. Configure routing. Add the default ASP.NET MVC global application class (Global Application Class) to Global.asax.

Using System; using System.Collections.Generic; using System.Linq; using System.Web; using System.Web.Mvc; using System.Web.Routing; namespace MixingBothWorldsExample {public class Global: System.Web.HttpApplication {public static void RegisterRoutes (RouteCollection routes) {routes.IgnoreRoute ("{resource} .axd / {* pathInfo}"); routes.IgnoreRoute ("{resource} .aspx / {* pathInfo}") Routes.MapRoute ("Default", / / Route name "{controller} / {action} / {id}", / / URL with parameters new {controller = "Home", action = "Index", id = ""} / / Parameter defaults) } protected void Application_Start () {RegisterRoutes (RouteTable.Routes);}

Note the following line of code that prevents requests from ASP.NET forms from being routed to ASP.NET MVC:

Routes.IgnoreRoute ("{resource} .aspx / {* pathInfo}")

After the above four steps are complete, we can begin to add ASP.NET MVC controllers and views, such as:

Using System.Web.Mvc; namespace MixingBothWorldsExample.Controllers {public class HomeController: Controller {public ActionResult Index () {ViewData ["Message"] = "This is ASP.NET MVC!"; return View () } the above is an example of the mixed use of ASP.NET forms and ASP.NET MVC in the same application shared by Xiaobian. If you happen to have similar doubts, please refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.