a8eb5bee70
The View Engine now needs to know about pages :(. This isn't ideal but the view engine needs to know what set of search paths to use. This was already hardcoded for controllers vs controllers + areas. It felt right to further hardcode instead of introduce a wierd abstraction that we only use. Additionally pages use a view location expander to implement an ascending directory search. |
||
|---|---|---|
| .. | ||
| ApiExplorerWebSite | ||
| ApplicationModelWebSite | ||
| BasicWebSite | ||
| ControllersFromServicesClassLibrary | ||
| ControllersFromServicesWebSite | ||
| CorsWebSite | ||
| ErrorPageMiddlewareWebSite | ||
| FilesWebSite | ||
| FiltersWebSite | ||
| FormatterWebSite | ||
| HtmlGenerationWebSite | ||
| Microsoft.AspNetCore.Mvc.TestConfiguration | ||
| RazorPageExecutionInstrumentationWebSite | ||
| RazorPagesWebSite | ||
| RazorWebSite | ||
| RoutingWebSite | ||
| SecurityWebSite | ||
| SimpleWebSite | ||
| TagHelpersWebSite | ||
| UserClassLibrary | ||
| VersioningWebSite | ||
| WebApiCompatShimWebSite | ||
| XmlFormattersWebSite | ||