Nugets, updating, local folder vs pack folder, etc

vvvv gamma question
1

Some question i’m having regarding Nugets

About vl.io.osc, @joreg, you told me to do : nuget install vl.io.osc -version 2.0.7 to test the newest version of io.OSC with bugfixs

Doing so seem to add the nuget to AppData/Local/vvvv/gamma-preview/nugets/
This i suppose override the current vl.io.osc i was using from programs/vvvv/vvv_gamma_{version}/packs/

I have a few questions :

  • In the preview build of VVVV, are the all the most recent nugets fetched to be included in the packs automatically ? (to always contain the most recent updated nugets)

  • Now that i have this nuget in my local folder (AppData/Local/vvvv/gamma-preview/nugets/), do this mean that even future VVVV build that contain newer version of vl.io.osc (in /packs) will still be overwitten by the one in my Local folder ?

  • In that case, would it make sense to clean my Local folder from the default library nuget after a new build is released ?

  • Bonus question, regarding all the non default nuget (not packed like vl.addons, VL.MediaPipe, VL.Devices.Kinect2), is there a way to update all theses automatically with a command ? Like fetch all the newest version of all my manually installed nugets ?
    Because it seem it would be something common for users to keep old versions of all theses and never update them ?

Thanks !

2
  1. We set the shipped versions manually. No auto-fetch-latest-
  2. Currently the rule is that the system will take the newest version it can find (either from it’s own shipped folder or your nuget folder). There are some exceptions to this rule, like for example packages vvvv core needs on its own. Have a look at the log for more information.
  3. You’ll have to clean the folder from time to time yes. Also note that you can pass a different folder with the command line argument --nuget-path - this is very helpful for projects where you want to have consistent package versions.
  4. No, there’s no such command.

In general we are aware that managing the locally installed packages across multiple vvvv versions and projects is far from optimal and we’re working on improvements in that area.

3 Likes
3

Thanks for all the answers !
Very helpful •ᴗ•