NOTE: This implementation does not create an MVC widget.
RECOMMENDATION: We do not recommend that you implement just the controller and the view without the associated model.
First, implement the controller:
RECOMMENDATION: To make sure you can easily differentiate between the Classic MVC controllers and widget controllers, we recommend that you place the Classic MVC controllers in the <root>/Controllers folder.
Next, implement the view:
RECOMMENDATION: To make sure you can easily differentiate between the Classic MVC views and widget views, we recommend that you place the Classic MVC views in the <root>/Views/<ControllerName> folder.
Once you build the project, the controller gets the service as a parameter to its constructor. When you request the domain/classic/<ControllerName>/ route, the controller is executed by the Classic MVC pipeline and returns the corresponding view.
Increase your Sitefinity skills by signing up for our free trainings. Get Sitefinity-certified at Progress Education Community to boost your credentials.
This free lesson teaches administrators, marketers, and other business professionals how to use the Integration hub service to create automated workflows between Sitefinity and other business systems.
This free lesson teaches administrators the basics about protecting yor Sitefinity instance and its sites from external threats. Configure HTTPS, SSL, allow lists for trusted sites, and cookie security, among others.
The free on-demand video course teaches developers how to use Sitefinity .NET Core and leverage its decoupled architecture and new way of coding against the platform.
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important