acd1cf3251
* Relayer MvcEndpointDataSource Separates the statefulness of the data source from the business logic of how endpoints are created. I'm separating these concerns because one of the next steps will split the MvcEndpointDataSource into two data sources. * Simplify MvcEndpointInfo Removing things that are unused and leftovers from the 2.2 design of this feature. * Remove per-route conventions Removes the ability to target endpoint conventions per-conventional-route. This was a neat idea but we have no plans to ship it for now. Simplified MvcEndpointInfo and renamed it to reflect its new purpose. * Remove filtering from MvcEndpointDataSource This was neat-o but we're not going to ship it like this. We're going to implement filtering in another place. Putting this in the data source is pretty clumsy and doesn't work with features like application parts that need to be baked in addservices * Simplify ActionEndpointFactory * Split up data sources * Use UseRouting in functional tests I've rejiggered our functional tests to de-emphasize UseMvc(...) and only use it when we're specifically testing the old scenarios. UseMvc(...) won't appear in templates in 3.0 so it's legacy. * Update templates * Add minor PR feedback * one more |
||
|---|---|---|
| .. | ||
| Controllers | ||
| SimpleWebSite.csproj | ||
| Startup.cs | ||
| readme.md | ||
readme.md
SimpleWebSite
This sample web project illustrates a minimal site using Microsoft.AspNetCore.Mvc.Core.
Please build from root (.\build.cmd on Windows; ./build.sh elsewhere) before using this site.