Why does not Asp.net mvc application work on Asp.Net Classic Application Pool? -

I have an ASP.Net MVC 2 web application that is deployed on .NET 4.0 on IIS 7.5. When I select the application pool as the asp.Net v4.0 classic , I get the following error.

  HTTP error 403.14 - The content of this directory is not configured to not list the prohibited web server  

When I press the application pool Asp.Net v4.0 integrated , then it works fine. Does anyone know what the reason is?

Update: I followed the steps of the following URL.

I've added a map for the .mvc extension and has modified the routing as shown below.

  route. IgnoreRoute ("{resource} .axd / {* pathInfo}"); New {controller = "home", action = "index", id = urlParameter, with routes ("default", // root name "{controller} .mvc / {action} / {id}", // URL parameter. Optional) // parameter defaults;); Routes MapRoute ("Root", "New", New {Controller = "Home", Action = "Index", id = ""}  

The following URL is working fine and I Home / Index page.

  http: //myapp/home.mvc  

but it returns the same error (HTTP error 403.14 -

Update

It is on a 7 Turbo Gold Premium Premium Bit system on IIS 7.5. The AAP pool was running in integrated mode. If I run my app in classic mode, then public access is given as it should be. So here's a question: How do I run it in unified mode if I want to?

With classic mode, you need to do wildcard mapping or use the ".mvc" extension. The name of your controller in the URI will therefore give you your IIS ASP. * .mvc mapping in NET configuration to . Do not or change your default route to do something like this:

  routes.MapRoute ("default", // root name "{controller} .mvc / {action} / {id}" , // parameter with new URL {controller = "home", action = "index", id = ""}, // parameter error zero);  

These methods certainly work; In fact, this is the only way to support IIS 5-6. On the other hand, I only use integrated mode with IIS 7.