For the last few years our standard architecture for .net web apps has been MVC. Our situation is that our organization has many MVC apps nested inside a number of content sites. We've recently hired a firm to move our content to SiteFinity from Ektron. So when their architect told me that SiteFinity didn't support MVC I called him on it. Then when I asked him to put it in writing He responded as follows:
"The confusion lies that Telerik has made an attempt to enter an MVC market with a web forms application. That is, they market the ability for developers to integrate MVC elements into their page model. Additionally, they support classic controller-driven content delivery within their application space, but otherwise functions independently of Sitefinity. This mainly exists as an option to integrate an existing MVC application within Sitefinity's application root. If you do have plans on migrating application code to the Sitefinity platform, though, we definitely need to discuss this as this would be cleanly out of scope for the original statement of work.
Since Sitefinity is otherwise engineered around the classic ASP.Net web forms page model, there is no plan to depart from that model for this project. Telerik isfirm in their business decision to support existing as well as develop all new features using web forms. The majority of resources available in support of Sitefinity are also forms based."
Is this true? Am I doing the right thing asking his company to deliver in MVC ?
You can without doubt migrate your MVC code. Go to apterainc.com and fill out a contact us form we would love to migrate MVC code! We are a platinum Sitefinty partner!