To delete an add-on, you uninstall the NuGet package, containing the add-on. You use the Package Management Console of Visual Studio in the following way:
.nupkg
RESULT: When Sitefinity CMS starts, it detects the missing add-on and removes all changes introduced by it, including all content, custom fields, modules, configurations, widget templates, etc.
To transfer the changes to the next environment from the Continuous delivery process, you transfer the ~\App_Data\Sitefinity\Addons folder to the next environments. This folder contains all installed add-ons and a registry for them - addons_registry.sf.
~\App_Data\Sitefinity\Addons
addons_registry.sf
IMPORTANT: Always deploy the registry file as well. If the registry file is not deployed, when Sitefinity starts in the next environment it will try to automatically generate a new registry based on the existing add-ons. This will lead to mismatch of the Development environment registry and the next environment registry. As a result, the deletion of an add-on will not be deployed.
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