While you can use definitions to control the behavior of Sitefinity’s backend with its built-in modules, you can also implement custom definition classes for your custom modules. This section is going to explain how you can do that.
The reason those three exist is rooted in the chain of responsibility pattern that definitions implement. The definition class is used to keep values for the properties of each control in memory. The configuration element is used to persist those values as a configuration file. The interface ensures that both the class and the configuration element implement the same contract (or have the same properties). You need to implement all three components if you want to use a custom definition for your control.
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 © 2020 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