Packages and dependencies

Imar Spaanjaars

Posted on 26/03/2017 17:32:31

Hi there,

I have a Live Integration project that depends on a number of Dynamicweb assemblies such as Dynamicweb.Ecommerce, Core, Environment and Extensibility. Instead of hardcoding references to these assemblies, I wanted to use their counterpart NuGet packages. However, when I install Dynamicweb.Ecommerce, I get lots of other references and dependencies as well, such as AbcPdf, Smart Search Mailing and a lot more.

Is there a way around that or is that by design? I can imagine the Dynamicweb.Ecommerce needs those to operate at runtime (during which all these assemblies will exist). I just don't need all that crap in my Visual Studio project ;-) Any way around it other than referencing the assembly directly?

Imar

Replies

Morten Bengtson

Posted on 27/03/2017 08:17:27

This post has been marked as an answer

Hi Imar,

When you install a package using the NuGet Package Manager in Visual Studio you have the option to ignore dependencies.
Just select "Ignore dependencies" under dependency behaviour (see attached screenshot).

In the NuGet Package Manager Console you can use this command:
Install-Package Dynamicweb.Ecommerce -IgnoreDependencies

We are continuously trying to reduce the number of dependencies (especially on "crap"), but it takes time :)

BR Morten

Votes for this answer: 1

Imar Spaanjaars

Posted on 28/03/2017 09:25:17

Thanks Morten. that makes a lot of sense. Hope I didn't insult anyone with the word crap. I should have said "all this great, value-adding third-party material" ;-)

You must be logged in to post in the forum

Developer forum

Packages and dependencies

Replies