Package Manager for VVVV
Clone or download


A package Manager for VVVV

Build status


In vvvv packs plugins and other externals are not coming in proper packages with meta information attached to them, usually they are just a collection of files at the right places extracted from an archive mostly. In itself it wouldn't be a problem as isolated packs are recognized and loaded into vvvv quite well. Problem starts when there are packs depending on X number of other packs. And with ~ 630 externals listed only on + more experimental, pre-release packs circulating on github that actually happens quite some time.

So user were supposed to hunt down dependencies and install them manually with varying success. (which btw would be ridiculous if you'd need to do the same with node.js or .NET libraries) This also scared pack developers to reference or use parts of other magnificent packs forcing them not to develop a feature to its full potential.

Not anymore!

vpm is a simple and also simple to use command line utility which supposed to automate this process through XML pack configuration files or .vpack files.
See in action here:

click here to watch on youtube


  • Recursive dependency installation
  • Stuff you would expect from a regular package Manager
    (Except for version checking YET)
  • Install packs directly from browser or anywhere with vpm:// and vpms:// uri schemes
  • Associate pack file with vpm.
  • C# scripting for installation and for packs which don't have a complimentary vpack file (yet ;) )
  • License Agreement screen for packs

How it works?

vpm first creates a temporary folder called (guess what) ".vpm" inside specified vvvv's folder. vpm will create working directories for each packs and dependencies in this temporary folder. These folders can be used by the installation scripts to download, clone or create data for the pack, and copy the results from those folders to vvvv\packs.
Then it will parse the input vpack file and its dependencies recursively. When that's done the user is prompted to accept the license agreements. If all the licenses have been agreed the installation scripts will be run for each collected packs/dependencies. Note that a vvvv instance is not required anymore so you can specify any, even a non-existing folder. vpm will ask you which architecture you want to use if it can't find a vvvv.exe in the specified folder. If there's no registered vvvv and no folder is specified vpm will use its containing folder.

Getting started for End-users

  • A registered vvvv is recommended (but not required anymore)
    (means run setup.exe and associate .v4p files at least once during the lifetime of current windows install)
  • Download latest version from here:
  • Extract anywhere
  • Run it at least once so it can register vpm:// or vpms:// uri schemes and associate .vpack files.
    (requires Admin privileges (UAC dialog box will pop up))
  • Now you can either double click a .vpack file or use a vpm(s):// url from browser
    (for example from the VPDB repo

Getting started for Power-users

or Command line arguments:

Argument Example Description
-vvvv -vvvv \Path\To\vvvv.exe Manually select a vvvv instead of a registered one. It works also if no vvvv is registered.
-q -q simply don't prompt user and go with default choices

Getting started for Pack developers

XML specification

The mandatory minimal vpack file and its structure looks something like this:

        // C# script here

However this vpack won't do anything as no instructions are written in the installation script. Here are the currently processed tags: (tags tagged with a * is mandatory)

<name>* will also serve as the default folder name and vpm will also determine if an earlier installment is already in the packs folder based on this name (... too, see aliases)

<aliases> is a list of possible alternative foldernames might containing current pack in vvvv's packs folder separated with commas. vpm checks if pack is already installed based on the name and aliases if any is specified.

<license> is a an url pointing to possibly a license agreement but it can be also used for allowing users to actually buy payed contributions. Contents of this url will be displayed on the EULA screen.

<source> It may specify a git repository which vpm will clone in its temporary folder. Otherwise the installation script have to take care of fetching pack data from the internet too. It is optional and it is rather recommended to use the GitClone method in the installation script.

<dependencies> The collection of <dependency> tags. Any other tags will be ignored by vpm here.

<dependency> is pointing to a pack which the current pack is relying on. Its child tags are

  • <name>* same as /vpack/meta/name just for dependency
  • <aliases> same as /vpack/meta/name just for dependency
  • <source>* can point to
    • a .vpack file with vpm(s):// format
    • a .csx file containing plain C# installation script with http(s):// format
    • a public git repository presumably containing a vpack file in its root with http(s):// format

<install>* is where the C# script goes which tells vpm what to do with afore-mentioned data. vpm is using C# Scripting language might be dubbed as Roslyn. You can find more on it at

Here's a real life example using most of the above mentioned tags for mp.dx

			VVVV.Dir + "\\packs\\" + Pack.Name,
			ignore: new string[] {"src", ".git*"}

License pages

In the vpack file you can specify a simple url pointing to any website. vpm provides some javascript functions which can allow the license page to communicate with vpm and pass data to the installation script. Such data can be used to select different editions of the same pack to install based on user input on the license page.

The page can disable vpm.disableAgree() or enable vpm.enableAgree() the "Agree and Install" checkbox, pass a string data to the installation script vpm.setInstallData(data) and it can automatically agree, advance to the next pack and pass string data to the installation script vpm.continue(data) with one function too. It can also read the current vpack xml file vpm.getPackXml().

The installation script can access the passed data via Pack.InstallDataFromJS which can be null or empty if the licensing page haven't written to it.

Note: Be careful what sorts of data you pass this way to the installer. Because vpm is open source one can easily look at this data with a Visual Studio debugger if they put breakpoints on the right functions. If you need to pass confidential data I'd suggest using an arbitrary encryption on it encoded in javascript wolrd and decoded in csx wolrd. Both are black boxes according to a simple debugger however again consider that the user can read csx source code in the vpack. So engineer it accordingly. To make this more secure base64 encoded compiled binary support is on the TODO list.

Installation scripts

Everything what's specified here you can do that with vpm too (in theory). It's full fledged C# (in theory) with a python inspired flavor. The only limit here is your dedication. vpm will create a separate "global" object for each installation script containing useful information and common easy to use methods for moving/fetching files around.
See VpmGlobals at src/vpm/scriptglobals.cs (line 108) to get an idea about what they are and how to use it. (proper docs coming soon to wiki)

Because of how Roslyn works you don't have to "verbally reference" the global object every time you want to access its members. They can be written out implicitly like this:

// instead of VpmGlobals.Pack.Name just
// or instead of VpmGlobals.GitClone(...) just

Here's a real-life example of the dx11-vvvv installation script

GitClone("", Pack.TempDir);
GitClone("", Pack.TempDir + "\\FeralTic");
GitClone("", Pack.TempDir + "\\girlpower");

BuildSolution(2013, Pack.TempDir + "\\vvvv-dx11.sln", "Release|" + VVVV.Architecture);

	Pack.TempDir + "\\Deploy\\Release\\" + VVVV.Architecture + "\\packs\\dx11",
	VVVV.Dir + "\\packs\\dx11"

Also other one for messages:

GitClone("", Pack.TempDir);

BuildSolution(2013, Pack.TempDir + "\\src\\vvvv-Message.sln", "Release|" + VVVV.Architecture, true);

	Pack.TempDir + "\\build\\" + VVVV.Architecture + "\\Release",
	VVVV.Dir + "\\packs\\vvvv-Message"
	Pack.TempDir + "\\build\\AnyCPU\\Release",
	VVVV.Dir + "\\packs\\vvvv-Message"


To make your pack available for the public you need to create your vpack file put it anywhere on the internet and create vpm link on your publishing surface (like or's) with this syntax. (Note: pure html links will work on articles/contributions too ;) )

<a href="vpm(s)://DOMAIN/PATH/PACK.vpack">My Awesome Pack</a>

vpm links are actually http urls just the http:// part is replaced with vpm:// (or https:// is replaced with vpms:// for secure connections).
For example a vpm link to mp.dx is

<a href="vpms://">mp.dx</a>

Apparently uri schemes other than http(s) is not working with github flavored markdown so I can't demonstrate here but you can get the point. :(

License is MIT aka "do whatever you want with it, no fucks are given"