You should add third party dependencies of the created add-on as NuGet package dependencies in the .nuspec file.
.nuspec
IMPORTANT: The add-on that you create cannot depend on the structure or the data of another add-on. You cannot create one add-on out of functionality installed by another add-on.
The recommended approach is to add a dependency to the Telerik.Sitefinity.All NuGet package in the add-on .nuspec file. Configure the dependency so that it allows for >= versions of Sitefinity CMS to be installed.
Telerik.Sitefinity.All
>=
EXAMPLE: <dependency id="Telerik.Sitefinity.All" version="9.2.6000.00" />
<dependency id="Telerik.Sitefinity.All" version="9.2.6000.00" />
NOTE: For custom cases where Sitefinity is not referenced via NuGet packages in the client app, you can create an add-on NuGet packages without depending on or including any Sitefinity CMS DLLs. In this case, the clients that install the add-on will have to manually add binding redirects, if their Sitefinity version is higher from the add-on’s dependent Sitefinity version. We do not recommend this approach, due to the unclear dependencies of the produced add-on.
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