You should add third party dependencies of the created add-on as NuGet package dependencies in the .nuspec file.
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.
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.
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