Let's use Central Package Management to simplify NuGet package updates (OSOE-567) about open-source-orchard-core-extensions

[sarahelsaig]

Won't that be a hassle with submodules? Every project using them would have to implement its own Directory.Packages.props file. Also how would that work during NuGet publishing?

[Piedone]

We tried centrally managing OC dependencies before, though not this with feature, just by adding the same dependencies to all projects with a props file. It wasn't worth it.

Due to what Dávid says, I don't think this would work at all with OSOCE projects. In other projects, I don't really see the benefit: It'd make managing project-level dependencies more complicated, and at most what we gain is removing duplication of Version attributes, but only that we get rid of a bit of XML. Otherwise, due to enforced consolidation during builds, we already use common versions of each dependency.

[0liver]

Both of you have good arguments. I guess I was somewhat blinded by the ✨ of this new, great feature, which it is for single-repo solutions.