aspnetcore/test/WebSites/RoutingWebSite
Ryan Nowak 46db71cfce Part 1 of fix for #2248 - Ambiguity when inheriting attribute routes
The change here is to make an attribute route defined on a base class
inherited only if no other routes were defined 'closer' to the controller
class.

To put another way, attribute routes can either be inherited or
overridden, you can't inherit + add your own.
2015-05-08 17:05:45 -07:00
..
Areas Update LICENSE.txt and license header on files. 2015-05-01 13:55:25 -07:00
Controllers Update LICENSE.txt and license header on files. 2015-05-01 13:55:25 -07:00
wwwroot
CountryNeutralAttribute.cs Update LICENSE.txt and license header on files. 2015-05-01 13:55:25 -07:00
CountrySpecificAttribute.cs Update LICENSE.txt and license header on files. 2015-05-01 13:55:25 -07:00
HttpMergeAttribute.cs Update LICENSE.txt and license header on files. 2015-05-01 13:55:25 -07:00
RoutingWebSite.xproj Part 1 of fix for #2248 - Ambiguity when inheriting attribute routes 2015-05-08 17:05:45 -07:00
Startup.cs Update LICENSE.txt and license header on files. 2015-05-01 13:55:25 -07:00
TestResponseGenerator.cs Update LICENSE.txt and license header on files. 2015-05-01 13:55:25 -07:00
project.json
readme.md

readme.md

RoutingWebSite

This web site illustrates how to use conventional and attribute routes.