asp.net MapPageRoute order of precedence

  • Thread starter Thread starter moke
  • Start date Start date
M

moke

I am attempting to use the MapPageRoute feature in Visual Studio 2010 and
..NET Framework 4.0.

What I have noticed is that if I define a page route called "Default" like
below and the page Default.aspx exists in the project, then the route does
not work.

routes.MapPageRoute("Default", "default.aspx", "~/Page2.aspx");
routes.MapPageRoute("Test", "test.aspx", "~/Page2.aspx");

If I change the name of the Default.aspx in the project to Default_1.aspx,
then the route works fine.

There seems to be some order of precedence going on. Is there a way to make
my route definitions evaluated first so I don't have to rename my pages to
use the routing engine?
 
Back
Top