Version Sitefinity 13.3
Sitefinity 14.0 BETA Sitefinity 13.3 Sitefinity 13.2 Sitefinity 13.1 Sitefinity 13.0 Sitefinity 12.2 Sitefinity 12.1 Sitefinity 12.0 Sitefinity 11.2 Sitefinity 11.1 Sitefinity 11.0 Sitefinity 10.2 Sitefinity 10.1 Sitefinity 10.0 Sitefinity 9.2 Sitefinity 9.1 Sitefinity 9.0 Sitefinity 8.2 Sitefinity 8.1 Sitefinity 8.0 Sitefinity 7.3 Sitefinity 7.2

Topics

All topics

MVC modes

Sitefinity CMS supports three MVC modes. The mode used depends on your development process as well as the functionality you want to implement. The following sections describe each mode.

Classic (bypass the Sitefinity CMS engine and directly use native controllers)

Classic mode is functionally equivalent to ASP.NET MVC. You can take regular controllers that you implemented in a non-Sitefinity CMS ASP.NET MVC project, include them in the Sitefinity CMS project, and register routes that use them. This mode lets you reuse a lot of legacy code that you may want to move from a regular application to a Sitefinity CMS application. In this mode, you do not work with Sitefinity CMS pages at all.

Working in Classic MVC mode is suitable when you need to implement a custom scenario with a very particular and specific functionality and behavior. For example, your scenario requires to implement a number of single-page-application pages that are constructed with SPA framework, such as Angular. 

Another example is when you are porting an existing MVC app into Sitefinity CMS, and want precise control over your URLs, you may want to use the Classic MVC mode.

You can read a detailed description of how you can use the classic mode in For developers: Classic MVC mode.

Pure (multiple controllers per page, page is MVC)

The pure mode lets you use MVC controllers and views as widgets on a Sitefinity CMS page. There is one major functional difference between pure and classic modes – you can use multiple controllers on the same page. Each controller becomes a widget on the page and is responsible for rendering a portion of it. You cannot use WebForms widgets on such a page.

An example of a scenario when you use Pure MVC mode is in case you need clear markup, a lot of client code and are willing to sacrifice the ViewState and postback model.

You can read a detailed description of how you can use Pure mode in For developers: Pure MVC mode.

Hybrid (Mix MVC and WebForms on the same page)

The Hybrid MVC mode goes even further than Pure MVC mode and lets you mix WebForms and MVC widgets on the same page. It has to keep all WebForms-related markup to enable ViewState, but it can also render the output of MVC controllers. There is one limitation – in your MVC controllers, you cannot use the regular BeginForm helper but should use the Sitefinity CMS helper instead. The reason is that the WebForms model can only allow a single form on the page.

You can read a detailed description of how you can use Hybrid MVC mode in For developers: Hybrid MVC mode.

Mode comparison table

Mode

Classic

Pure

Hybrid

Uses a Sitefinity page

No

Yes

Yes

Uses ViewState (clean markup)

No

No

Yes

Controllers per page

1

Many

Many
Sitefinity CMS Forums widgets No No Yes
Sitefinity CMS Ecommerce widgets No No Yes

Form helper

@Html.BeginForm

@Html.BeginForm and @Html.BeginFormSitefinity

RECOMMENDATION: We recommend that you use the @Html.BeginFormSitefinity helper since it ensures that you can use your widget on both hybrid and pure pages.

@Html.BeginFormSitefinity

 

Route registration

Manual

Auto

Auto
 

Want to learn more?

Sign up for our free beginner training. Boost your credentials through advanced courses and certification.
Register for Sitefinity training and certification.

Was this article helpful?

Next article

Create custom models, controllers, and views in Classic MVC mode