AI OnAI Off
That is the default behavior of nuget NuGet Package Dependency Resolution | Microsoft Docs (lowest compatible version)
In previous version of VIsual Studio I think you have the option to change that, however it is no longer available in 2022 as I checked it
Magnus Rahl has written an in-depth article about how nuget dependencies are resolved with the new model.
We ended up referencing a handful of packages in order to get to the latest versions.
I think I've often ended up referenceing more than a handful of packages, but an Optimizely engineer once recommended me directly installing the following packages.
What's the preferred way to handle packages in CMS 12?
At the moment I only have EPiServer.CMS referenced and all dependencies are handled automatically. That seems to keep the dependencies at the lowest possible version though.
Any suggestions about this?
/Mikael