vvvv allows you to export a patch into an executable, standalone program. In order to do so, open the Application Exporter via
Quad > Export....
- Application to export: Choose which application to export (in case you're working on multiple projects at the same time)
- Output directory: Choose where the exported program and files will be created
- Press the Export button and wait until the green progressbar is full and the Run button becomes available
- Press Run to test/run your program
- Explore Output: opens a file explorer at the specified output directory
After a successful export, the output directory will contain a directory with the name of your application. Inside this directory you find the executable. To run the program on another PC you need to copy the whole content of this directory.
Next to the application directory you'll also find a
\src directory. This is an artefact that vvvv creates during export and can be safely deleted.
.NET developers may find this interesting though, as it contains a completely valid c# solution of the exported project that can be opened, viewed and modified with Visual Studio.
Choose between Windows or Console app. A Console app will open a windows Console and run the Update operation for only one frame, then immediately Dispose itself. So in order to keep it running you need to take care of blocking the operation yourself. You can do that for example by running your program in an endless loop...
- Args [System] to access commandline arguments the app was called with
- Nodes from the advanced [System.Console] category
- Terminal.Gui for creating applications with a text based UI
Disable to export for 32bit architectures.
If active, removes artefacts of previous exports (ie. deletes the \src folder) before exporting. This will cause exports to take longer but also makes sure previous artefacts don't interfere with the new export.
Using referenced external assets in exported executables for now is a bit cumbersome:
Instead of using path IOBoxes to reference files, you have to use a combination of the node ApplicationPath and a string of the relative path to your asset. Also after export you have to manually copy the assets to the output directory!
During development a path created like that will be relative to your main .vl document. When exported, it will be relative to the executable.
Configuring a renderers appearance
Referencing the nuget VL.CoreLib.Windows adds the following nodes:
- SetWindowState and WindowState
These allow you to configure the renderers caption, controlbox, framing and more.
In order to have your executables to run without a warning on other PCs, you need to sign them with a certificate using SignTool.
In case the export fails, the console will be opened to show there was an error.
Please send us the console output by pressing "Copy To Clipboard" and pasting it to us via forum or chat.