Stride nuget fetches transitive dependencies

vvvv gamma question
1

Hi, need suggestion, not sure what to do to reduce maintenance hell…

So i have:

<?xml version="1.0"?>
<package xmlns="http://schemas.microsoft.com/packaging/2011/10/nuspec.xsd">
  <metadata>
    <id>VL.Stride.Voxels</id>
    ...
    <!-- <dependencies>
      <group targetFramework=".net8.0">
        <dependency id="Stride.Voxels" version="4.2.1.2487"/>
      </group>
    </dependencies> -->
    ...
</package>

The problem if I uncomment that I will have all of the stride effectively fetched in the nuget folder…

For now i just advise users to use:

nuget install Stride.Voxels -Version 4.2.1.2487 -DependencyVersion Ignore

But that feels bit unstable in terms of maintainance…

The gpt suggests bundle dll directly, i’m thinking maybe we can instead include this package to VL.Stride.Runtime?

2

These things should be dealt with far better with upcoming package management. Our system will internally do a package restore via nuget on the full dependency graph - so it should be able to deal with the situation that your package references an older version of Stride than what current running vvvv is referencing.
So I’d say keep your dependencies in your nuget.