Forums

Home / Developer Network / Forums / Sitefinity 3.x: Suggestions > Support for ASP.NET MVC

• Paul

  Posted on Nov 5, 2009 (permalink)

  Hello,

  
  

  Any plans to build a new CMS framework on top of ASP.NET MVC?  

  
  

  -Paul

  Reply

• Ivan Dimitrov Ivan Dimitrov

  Posted on Nov 5, 2009 (permalink)

  Hello Paul,
  
  We have plans for future implementations, but it will not be earlier then Sitefinity 4.0 which will be released next year.
  
  Sincerely yours,
  Ivan Dimitrov
  the Telerik team

  
  Instantly find answers to your questions on the new Telerik Support Portal.
  Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

  Reply

• Paul

  Posted on Nov 5, 2009 (permalink)

  Ivan,

  
  

  Thanks for the response.  We are evaluating CMS systems right now.  We thought about building our own CMS on top of MVC, but couldn't justify this as a top priority.  If you get something like this to market quickly, we would strongly considering purchasing it.  

  
  

  Thanks,

  
  

  Paul

  
  

  Paul

  Reply

• Adam

  Posted on Dec 24, 2009 (permalink)

  Hi Guys,
  
  Any news on where Sitefinity is at in relation to MVC? Are there any examples of developers incorporating MVC into an existing sitefinity (3.x-4.0) project?
  
  Thanks!
  

  Reply

• Ivan Dimitrov Ivan Dimitrov

  Posted on Dec 25, 2009 (permalink)

  Hello Adam,
  
  In 3.x versions there is no API that could allow you to make MVC integration. As written above we will expose some functionality no more that 4.0 release, most probably in 4.1 or one of the SP.
  
  Sincerely yours,
  Ivan Dimitrov
  the Telerik team

  
  Instantly find answers to your questions on the new Telerik Support Portal.
  Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

  Reply

• Luke Durrant

  Posted on Apr 27, 2010 (permalink)

  Hey there,
  
  is ASP.NET MVC still planned for around 4.1?
  
  Luke

  Reply

• Bob Bob

  Posted on Apr 28, 2010 (permalink)

  Hi Luke,
  
  

  Let me first clarify our approach.

  Although Sitefinity 4.0 does not use ASP.Net MVC framework, it follows very similar pattern in regards of separation of concerns. Actually, the entire backend UI and architecture follows MVVM pattern. We are soon going to provide SDK for easer custom modules creation based on our model. However, Sitefinity does not limit you to using this model only. You are free to build your Sitefinity applications in variety of designs.

  We do have plans to add support for ASP.Net MVC, but that is with low priority for the time being.
  
  Regards,
  Bob
  the Telerik team

  
  Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.

  Reply

• Bryan

  Posted on Jan 31, 2011 (permalink)

  Any updates worth mentioning since the last comment last April?

  Reply

• Gabe Sumner MVP

  Posted on Jan 31, 2011 (permalink)

  It's still low priority from everything I've heard.  There are other items (e-commerce, richer analytics, platform targeting, multi-variant testing) that have a lot more real-world business value.
  
  --
  
  Here is my perspective; I want Sitefinity to be accessible (recognizable) to a wide developer audience, Consequently, I'm hesitant to align with a technology that is unfamiliar to most ASP.NET developers. 
  
  --
  
  I would be more interested in hearing about project challenges that you're unable to address using the MVVM pattern Bob described above.  Having these facts makes it easier to justify this item on the roadmap.  
  
  Thoughts?
  
  Gabe Sumner
  Telerik | Sitefinity CMS

  Reply

• Luke Durrant

  Posted on Feb 1, 2011 (permalink)

  Gabe,
  
  From a developers point of view MVC is far superior when compared to windows web forms.
  and I can't agree with you saying that .NET MVC is a technology that is unfamiliar to most .NET developers I believe most developers are very aware and prefer .NET MVC but old projects stop the transition, well at least in my neck of the woods they do.
  
  I don't think its a mater of project challenges that can't be addressed its more getting it done is a way that doesn't make the next developer pull his/her hair out from working on the project. .NET MVC usually means less and therefore nicer code.
  But hmm lets not get into a MVC versus webforms battle
  for more checkout
  http://www.matthidinger.com/archive/2010/02/17/why-i-love-asp.net-mvc.aspx
  
  
  
  

  Reply

• fran

  Posted on Feb 15, 2011 (permalink)

  I totally agree with Luke. Even microsoft is more focused on using MVC framework rather than using the WebForm framework: you only need to take a look in codeplex how many things are going on under the mvc tag. I'd say that any developer that has programmed using MVC, he doesn't want to look back to WebForms. Of course everything can be address by WebForms, but the difference is on the "way" to do it. I think telerik is going loose the momentum, and they are not listening to the developer community, but only listening to the business people. Nokia didn't listen to their developer communitiy, and now see what it happens to them ...
  
  I hope you at least come up with some kind of mixed mode of working, allowing working using the MVC model, at least for the public pages. I could live with the backend stuff based on WebForms, but not my real web, not the data that I really care.

  Reply

• Gabe Sumner MVP

  Posted on Feb 15, 2011 (permalink)

  I think telerik is going loose the momentum, and they are not listening to the developer community, but only listening to the business people.
  
  It might be on a roadmap somewhere, but I doubt seriously MVC will be addressed this year.  There are simply too many other high priority items on the agenda.
  
  As I already mentioned, the audience for this technology is still comparatively small.  I know Luke mentioned that "most developers know MVC", but we have access to sales statistics (we have an MVC product) and research on this subject.  MVC may or may not be the next big thing, but if you want to engage with most .NET developers then this is not a good choice today.  Consequently, we are listening to the developer community.   
  
  I like the idea of supporting both approaches, but I have no idea how that would work.  Either way, in 2011 our focus will be spent on adding functionality to Sitefinity.  
  
  Here a few of the things on the 2011 roadmap:
  
  - Ecommerce
  - Advanced Analytics
  - Improved mobile support
  - A/B testing, multi-variant testing
  - Marketing automation 
  
  Features like these solve modern business challenges that organizations are struggling with.  MVC, by contrast, is simply an alternate way to do what we already do.  It's not a good use of time when contrasted with these other tasks.  It won't empower organizations do anything they aren't already doing.  Furthermore, we're likely to alienate lots of developers in the process.
  
  Gabe Sumner
  Telerik | Sitefinity CMS

  Reply

Home / Developer Network / Forums / Sitefinity 3.x: Suggestions > Support for ASP.NET MVC