This repository has been archived by the owner on Dec 14, 2018. It is now read-only.
Allow a way to modify locations in which views are looked for without having to modify ViewEngine #1039
Comments
pranavkm
changed the title
Allow a view to modify locations in which views are looked for without having to modify ViewEngine
Allow a way to modify locations in which views are looked for without having to modify ViewEngine
Aug 19, 2014
Also:
|
@pranavkm please set up a design meeting for this. |
pranavkm
added a commit
that referenced
this issue
Sep 5, 2014
…tions without changing the view engine. Fixes #1039
pranavkm
added a commit
that referenced
this issue
Sep 5, 2014
…tions without changing the view engine. Fixes #1039
pranavkm
added a commit
that referenced
this issue
Sep 5, 2014
…tions without changing the view engine. Fixes #1039
pranavkm
added a commit
that referenced
this issue
Sep 19, 2014
…tions without changing the view engine. Fixes #1039
pranavkm
added a commit
that referenced
this issue
Sep 19, 2014
…tions without changing the view engine. Fixes #1039
pranavkm
added a commit
that referenced
this issue
Sep 30, 2014
…tions without changing the view engine. Fixes #1039
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In Mvc 5, the VirtualPathProviderViewEngine that was the base for all view engines that shipped in the box looked for views in a very specific set of locations that were exposed as properties of that type.
The primary way to use customize rules for discovering view locations was by sub typing and changing the result of these properties. This feature work is designed towards finding a nicer way to go about this:
Proposal: View Location Expanders
["/Views/{1}/{0}", "/Views/Shared/{0}"]
RazorViewEngine
calls into these expanders to get all possible locations to locate views as part ofFindView
andFindPartialView
.cc @yishaigalatzer / @loudej
The text was updated successfully, but these errors were encountered: