The Sitefinity Documentation say, "All MVC artifacts in Sitefinity should be stored under the Mvc folder". Does this apply when using MVC Areas? I'm at the point where I am starting to believe there is something about MVC that requires the Area folder to be a root folder of the web application. Can you please either post or provide a link to a sample that uses Areas inside the Mvc folder?
The problem I have with the BugTracker application is that it does not comply with another documentation article that states, "All MVC artifacts in Sitefinity should be stored under the Mvc folder".
1. Is there something about the way Sitefinity is programmed that would make my code run differently if I were to put my MVC artifacts in a folder named something other than "Mvc". For instance, what if I were to use my company name instead of "Mvc" for the folder name?
My concerns are:
1. The BugTracker application may have been written prior to Sitefinity requiring "all MVC artifacts be under Mvc folder."
2. Eventhough the BugTracker application works outside the Mvc folder, a larger more complex application may not.
Can you please address my questions and concerns?
MvcControllerActionInvoker : ControllerActionInvoker
var areaName = proxyControl.Controller.GetType().FullName.Split(
Global : System.Web.HttpApplication
sender, EventArgs e)
Bootstrapper.Initialized += Bootstrapper_Initialized;
sender, Telerik.Sitefinity.Data.ExecutedEventArgs e)
Does this still apply for Feather Widgets within Sitefinity 8.1?
I'd like to use Areas, but I'm not sure how to configure this right. Should Areas be placed under the root, or under /Mvc ? Also, do we need to use the MvcControllerInvoker, or is it enough to use the AreaRegistration class?
Anyway, it doesn't work :(
I guess when using Feather, we need to inherit from the FeatherActionInvoker instead of the ControllerActionInvoker?
What is not clear is where to place the Area folder: inside the MVC folder or under the root folder?
I created a new ActionInvoker based on the FeatherActionInvoker, and now it seems to work fine. I can create areas which contains Feather Widgets. Great!
A problem that occurs now is that when I create new designer windows for my Feather widgets, they are not picked up by the widget. So it only works if I place the designer and the scripts under the /Mvc folder.
How can I make sure that designers and scripts are loaded when they are also placed under the Areas folder?
Should I do something with the DesignerUrlAttribute to make this work?
Hi Daniel, did you solved all this problems?
We'd like to use Areas but I'd like to make sure that this is trouble-free before trying :S
No, unfortunately I do not have a solution for this. However, it works fine as how I described it.
Maybe if the widgets and areas are in a separate project. I didn't try that.
Thanks! We have a separate project for custom MVC form controls, but I'm trying to avoid having different projects in this particular case, as cross-references already arise.
Areas would be enough for us, but of course form fields require scripts and designers and having those folders spread inside the area folder and also in the main Mvc folder is not ideal.
Do you have any advice in this case?
Yes, in fact the MVC form fields are Feather widgets, but they still have to go inside the main Mvc folder.
I've gave it a second thought and keeping it in a separate project seems to be the best option for us.
Are you also using Feather in this project? That might be an option to isolate different components?