Timeline for DD4T with MVC 5 and areas
Current License: CC BY-SA 3.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 19, 2014 at 22:24 | vote | accept | ToddB | ||
| Jun 18, 2014 at 19:51 | comment | added | Alvin Reyes | Okay that does help. When it comes up I'll see if there are relationships, keeping the "matching paths" part in mind. | |
| Jun 18, 2014 at 18:18 | answer | added | ToddB | timeline score: 11 | |
| Jun 18, 2014 at 14:15 | history | edited | ToddB | CC BY-SA 3.0 |
added 1775 characters in body
|
| Jun 18, 2014 at 10:41 | history | tweeted | twitter.com/#!/StackTridion/status/479212216801955840 | ||
| Jun 18, 2014 at 9:05 | comment | added | Ant P | @AlvinReyes You could certainly add some custom routes to map certain URL structures to Area-specific DD4T controllers but the obvious limitation there is that translation of structure groups will break the routing. It's difficult to elaborate without more context as what limitations will be encountered depend entirely on how Areas (as a development tool) are being utilised, which is a little too open-ended to constrain to a useful set of "options." If Todd were to elaborate a little on what problem he's thinking of solving using Areas, the question would be much easier to answer. | |
| Jun 18, 2014 at 8:56 | comment | added | Ant P | But these are two different questions. | |
| Jun 18, 2014 at 8:55 | comment | added | Ant P | trying to hit "\Views\Page\Default.cshtml" - you don't "hit" a view in MVC, you hit a controller action. It's not clear what you're trying to do, nor how this relates to your original question. If you are having a specific problem with your DD4T setup, post the relevant details in your question. If you want general information on what the likely obstacles to using areas are, you'll need to elaborate in your question on how you plan to use them because - in the typical scenario - there would be no relationship between DD4T and your MVC Areas; they would be completely independent. | |
| Jun 18, 2014 at 1:48 | comment | added | ToddB | I think I found the issue. In the DefaultComponentPresentationRender.RenderComponentPresentation method there is this call. controller = ConfigurationHelper.ComponentPresentationController. This gets the CompnentPresentationController name from the config file which can only be one and is the default one in the default MVC path. Still trying to verify. | |
| Jun 18, 2014 at 1:21 | comment | added | ToddB | Just to clarify a little. This is the error I get. "No route in the route table matches the supplied values." trying to hit "\Views\Page\Default.cshtml". The right controller is hit but the wrong page path are there is no "area" in front of the page. | |
| Jun 18, 2014 at 1:04 | comment | added | ToddB | I have different partner groups and want to have an area for each one to help keep viewers organized (I will have close to 100 views). So far in trying setting up a area route to a new page controller and clarifying by namespace works. However the RenderComponentPresentaion call fails say it can't find an instance and the path is not to the area view. | |
| Jun 18, 2014 at 0:58 | comment | added | Alvin Reyes |
These would be the Areas found under Visual Studio's Add Scaffold dialog and roughly represent website "sections" or maybe types of pages. @AntP, any thoughts on a relationship to Tridion Structure Groups or Page Types for MVC areas, perhaps? Or would the use of areas be up to development?
|
|
| Jun 17, 2014 at 22:07 | comment | added | Ant P | How do you plan to make use of areas? Generally speaking there should be no issues as they will be routed independently of your DD4T controllers. Also worth noting that areas have been around (and fundamentally the same) since MVC2. | |
| Jun 17, 2014 at 20:43 | history | edited | Nickoli Roussakov | CC BY-SA 3.0 |
minor word smithing
|
| Jun 17, 2014 at 20:40 | history | asked | ToddB | CC BY-SA 3.0 |