Try our conversational search powered by Generative AI!
AI OnAI Off
Debugging missing dependencies for addon packages
Hello Dan.
This is fixed in 7.5. If you have the add-on package file, you can try to install it using the “Manual Upload” option in the Add-On system UI. It reports some details when it fails.
Dec 04, 2013 12:26
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
The addon store in episerver 7 will only display the addons that can be installed (whos dependencies can be fulfilled). If you have a dependency that cannot be found then the addon will not be displayed.
So far so good.
If I would like to understand what dependency that fails then I can activate logging for the EPiServer.Packaging logger. I'll get something like below.
2013-12-03 14:37:24,494 [24] DEBUG EPiServer.Packaging.SitePackageInfoLoader: Checking if package can be installed: 'ImageVault.AddOn.EPiCMS7 4.3.10.2098-Development'.
2013-12-03 14:37:24,506 [24] INFO EPiServer.Packaging.Walkers.SiteUpdateWalker: SiteUpdateWalker: Attempting to resolve dependency 'CMS (≥ 2.0.39 && < 3.0)'.
2013-12-03 14:37:24,525 [24] INFO EPiServer.Packaging.Walkers.SiteUpdateWalker: SiteUpdateWalker: Attempting to resolve dependency 'EPiServer (≥ 7.0 && < 8.0)'.
2013-12-03 14:37:24,541 [24] INFO EPiServer.Packaging.Walkers.SiteUpdateWalker: SiteUpdateWalker: Attempting to resolve dependency 'EPiServer.Shell (≥ 7.0 && < 8.0)'.
2013-12-03 14:37:24,557 [24] INFO EPiServer.Packaging.Walkers.SiteUpdateWalker: SiteUpdateWalker: Attempting to resolve dependency 'EPiServer.Packaging (≥ 2.1.90.0 && < 3.0)'.
2013-12-03 14:37:24,573 [24] INFO EPiServer.Packaging.Walkers.SiteUpdateWalker: SiteUpdateWalker: Attempting to resolve dependency 'EPiServer.Framework (≥ 7.0 && < 8.0)'.
2013-12-03 14:37:24,591 [24] INFO EPiServer.Packaging.Walkers.SiteUpdateWalker: SiteUpdateWalker: Attempting to resolve dependency 'EPiServer.Packaging.Patch1'.
2013-12-03 14:37:24,614 [24] INFO EPiServer.Packaging.Walkers.SiteUpdateWalker: SiteUpdateWalker: Attempting to resolve dependency 'Shell (≥ 2.1.90.0 && < 3.0)'.
2013-12-03 14:37:24,651 [24] INFO EPiServer.Packaging.Walkers.SiteUpdateWalker: SiteUpdateWalker: Attempting to resolve dependency 'ImageVault.EPiServer7 (≥ 4.3 && < 5.0)'.
2013-12-03 14:37:24,667 [24] INFO EPiServer.Packaging.Walkers.SiteUpdateWalker: SiteUpdateWalker: Attempting to resolve dependency 'Meridium.Lib (≥ 1.4 && < 2.0)'.
2013-12-03 14:37:24,686 [24] INFO EPiServer.Packaging.Walkers.SiteUpdateWalker: SiteUpdateWalker: Attempting to resolve dependency 'log4net (= 1.2.10)'.
2013-12-03 14:37:24,708 [24] INFO EPiServer.Packaging.Walkers.SiteUpdateWalker: SiteUpdateWalker: Attempting to resolve dependency 'HtmlAgilityPack (≥ 1.4.6 && < 2.0)'.
2013-12-03 14:37:24,729 [24] INFO EPiServer.Packaging.Walkers.SiteUpdateWalker: SiteUpdateWalker: Attempting to resolve dependency 'Newtonsoft.Json (≥ 4.5 && < 5.0)'.
2013-12-03 14:37:24,751 [24] DEBUG EPiServer.Packaging.SitePackageInfoLoader: Package can not be installed: 'ImageVault.AddOn.EPiCMS7 4.3.10.2098-Development'.
Here I can see that the package manager checks if the ImageVault.AddOn.EPiCMS7 package can be installed and that it tries to resolve a couple of dependencies. After each dependency has been checked, the result is that the package cannot be installed.
To my question. How can I know what dependency failed? (In this case Meridium.lib.dll was not present in the bin folder). Can the result of each dependency be logged so it is easier to check?
/Dan