Hey all!
I’ve recently stumbled over some nice workflows in the chat to set up a VL project that manages the vvvv version and project NuGets, allows the use of package-repositories (like custom forks VL.Fuse or other internal libs) and lays out a basic structure to manage file dependencies. Special thanks to @readme then to properly set that up with me and walk me through some core concepts!
Like this, it is really nice to work with other contributors on a project together - everyone opening the batch file is opening the same project with the same vvvv and NuGet versions. No more conflicts with NuGet dependencies, the project will run on any computer. Just clone the project, download and install the right vvvv version, open the batch file and you’re good to go.
Please let me know if there are additional techniques or other improvements you would like to add or discuss!
Side note
It is still quite a nightmare to find out workflows and solutions like this. As the vvvv community exists since early beta days, I have the feeling that everyone just thinks this kind of stuff is common knowledge. But it actually isn’t - Gamma and VL are still new chapters, and if you are relatively new to vvvv like me, it is a crazy paper chase to dig through the docs, endless GitHub repos, the chat and the forum to put all the pieces together. I know that many VL developers are doing this kind of stuff with batch files and things, but why is nobody taking the time to properly introduce methods like that to newcomers?
And please leave a star on GitHub! I am confident that following each other and starring VL repositories will make a huge difference for the overall visibility of vvvv, VL and the community!