Add-ons should distribute a single piece of functionality to many consumers to solve a common set of problems across a wide range of web applications. Each add-on should have an owner who can maintain it and issue new versions.
RECOMMENDATION: We recommend using add-ons only in cases when you need to solve a common problem across many web applications. We do not recommend creating an add-on for every piece of customization of your system. Implementing an add-on for every piece of functionality in a system is not feasible and not recommended, as it can add significant complexity in the upgrade process and increases the overall development cost.
Add-ons are contained and distributed in NuGet packages. The .nuspec file and folder structure for each package is automatically generated by the Sitefinity CMS. The folder structure contains files with all structure and content data of the exported types. All custom developed functionalities, such as Providers, Widgets, HttpHandlers, Services, etc. are contained in separate projects that are referenced in the .nuspec file. The produced NuGet package contains all necessary custom code and data that works out-of-the-box when installed.
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 © 2019 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