Routing for View Pages

[pranavkm]

Routing

By default, the route for each page is mapped at it's application relative path (with the cshtml extension). The file name Index is optional and has the same behavior as routing to an action named Index in conventional routing i.e.
/Home/Index and /Home are equivalent. The optional value of the@page directive can be used to append a suffix to this route. Consider,

Page	Directive	Routes
/About.cshtml	@page	http://myappdomain.net/About
/Contact.cshtml	@page "location/{zip}"	http://myappdomain.net/Contact/location/98052
/Catalog/Index.cshtml	@page	http://myappdomain.net/Catalog http://myappdomain.net/Catalog/Index
/Catalog/Books.cshtml	@page "{id?}"	http://myappdomain.net/Catalog/Books/ http://myappdomain.net/Catalog/Books/12

Friendly urls

Associated with each page is an application model type similar to ControllerModel. We'd build on top of this to provide simple runtime configuration of routes. For instance, to configure an additional route to the /Catalog/Books.cshtml, here's what the Startup code might look like:

services
    .AddMvc()
    .AddRazorPages(options =>
    {
        options.MapPageRoute("Books/{id?}", "/Catalog/Books.cshtml");
    });

[pranavkm]

cc @DamianEdwards \ @rynowak

[mikebrind]

@pranavkm The MapPageRoute method doesn't exist on RazorPageOptions in Preview 1.0. Has this configuration option been moved somewhere else? Not included at all? If not, are there still plans to include it?

[pranavkm]

@mikebrind - doesn't look like I did any of the work for making friendly urls work - must've missed it. @rynowak - are we still on for adding a convention extension to register additional routes?

[pranavkm]

Also cc @DamianEdwards

[DamianEdwards]

Oops. This is meant to be there. Can we create a new issue to track this work and triage it into the next milestone please? We're out of time to do it in this one.