Default RenderMvcController per domain, or one for multiple doctypes
I have an installation with a couple of sites (siteA, siteB, siteC) and 20 or so document types (siteATextPage, siteBTextPage, siteCTextPage...)
Now I like to structure my views in subfolders. If I create custom controllers for each document type - I will get different paths for all document type views. /Views/SiteATextPage/ /Views/SiteBTextPage and so on.
Which is okay. But this will mean I have to setup a controller for every documenttype. Right?
It might be nice to be able to add an attribute to make the controller hook up for multiple documenttypes.
[ForDocumentTypes("siteATextPage,siteANewsPage,siteAFoo")] public class SiteAController:RenderMvcController
Or - one default controller per domain.
Or - would I accomplish this (fairly) easily by setting up custom routes (+ one controller per domain)?
Default RenderMvcController per domain, or one for multiple doctypes
I have an installation with a couple of sites (siteA, siteB, siteC) and 20 or so document types (siteATextPage, siteBTextPage, siteCTextPage...)
Now I like to structure my views in subfolders. If I create custom controllers for each document type - I will get different paths for all document type views. /Views/SiteATextPage/ /Views/SiteBTextPage and so on.
Which is okay. But this will mean I have to setup a controller for every documenttype. Right?
It might be nice to be able to add an attribute to make the controller hook up for multiple documenttypes.
[ForDocumentTypes("siteATextPage,siteANewsPage,siteAFoo")]
public class SiteAController:RenderMvcController
Or - one default controller per domain.
Or - would I accomplish this (fairly) easily by setting up custom routes (+ one controller per domain)?
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.