1. Sitefinity 4 is a web application and its model (MVVM
) is different from the MVC model and currently there is no integration with MVC.
2. Sitefinity uses OpenAccess
for database access.
3. It depends on the already existing application. Content items in Sitefinity can be created trough the API. Create a page with the API
reading the page title and the url from a collection and creating widgets reading the content from a source. Unfortunately there is no one click migration.
4. When a module is created for Sitefinity you need to deploy its .dll file without the project files (.cs, aspx, .resx)
5. With Sitefinity the project files are needed. This is App_Data, bin, ClientBin, web.config and all folder under the mentioned.
6. You can perform customization to widget templates and managing files from the cms backend, but if you want to add new web control to the project you must use visual studio if you are using Sitefinity as web application(adding new control requires Build (F6)) or just deploy the .ascx file and its codebehind if you use Sitefinity as website project.
7. Refer to answer 3.
All the best,
the Telerik team
Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking
system and vote to affect the priority of the items