Deployment of ASP. net mvc Beta

Step 1: deploy on IIS 5.1

IIS5.1 is IIS under XP.

The first thing to note is that asp.net mvc beta does not use System by default. web. abstractions. dll, System. web. routing. dll, System. web. mvc. dll private deployment of these three sets. If asp.net 3.5 SP1 is not installed on the server, use private deployment for these three sets, that is, it is deployed in the bin directory together with the website program.

Second, IIS5.1 cannot set wildcards or configure Handler like IIS7. However, you can configure Routing to send requests to the ISAPI Filter of asp.net for processing, such as in Global. asax. the configuration in cs can be as follows:

 
 

  
  
Code Snippet  
  
  
routes.MapRoute(  
  
  
 "Default",  
  
  
 "{controller}.aspx/{action}/{id}",  
  
  
 new { controller = "Home", action = "Index", id = ""}  
  
  
);  
 
 

Step 2: deploy on IIS 6

Microsoft asp.net mvc beta IIS6 deployment settings are as follows:

Click the configuration button here.

 

Click the insert button to insert the isapi of. net2.0 to the wildcard application ing half of the new window.

 

Check whether the file exists. Do not select it. Otherwise, the setting will be useless.

After the preceding settings are complete, mvc can exist as a directory. Excellent performance.

However, it is important to note that resource fees will be charged after this configuration, because all requests must be handed over to iis for processing.

In this way, the deployment of asp.net mvc beta is solved.

1. Introduction to ASP. net mvc Framework
2. Introduction to MvcAjaxPanel in ASP. NET MVC
3. ASP. net mvc Framework to save UpdatePanel
4. Use ASP. net mvc source code to find a solution
5. ActionInvoker of ASP. net mvc Framework