Sign In| Join
Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Contributor
7064 Points
1444 Posts
Apr 03, 2008 12:43 PM|LINK
With IIS6 you need a .mvc extension in each route so IIS6 knows to let ASP.NET process the request.
So rather than:
"flight/{flightNumber}""flight/{date}/{flightNumber}""flights""flights/active"
you need:
"flight.mvc/{flightNumber}""flight.mvc/{date}/{flightNumber}""flights.mvc""flights.mvc/active"
Note, you can manage without the .mvc using a wildcvard mapping, but this means handling all non-ASP.NET file types (.css, .html, .js, ...) within ASP.NET (i.e. create handlers) as well.
rjcox
Contributor
7064 Points
1444 Posts
Re: Deploying on IIS 6
Apr 03, 2008 12:43 PM|LINK
With IIS6 you need a .mvc extension in each route so IIS6 knows to let ASP.NET process the request.
So rather than:
"flight/{flightNumber}""flight/{date}/{flightNumber}"
"flights"
"flights/active"
you need:
"flight.mvc/{flightNumber}""flight.mvc/{date}/{flightNumber}"
"flights.mvc"
"flights.mvc/active"
Note, you can manage without the .mvc using a wildcvard mapping, but this means handling all non-ASP.NET file types (.css, .html, .js, ...) within ASP.NET (i.e. create handlers) as well.