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.
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important
Copyright © 2022 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.
Powered by Progress Sitefinity