i made a ready to go template repo quite a while ago but it should still do the thing.
its basically a vvvv-plugin template repo which you clone if you want to start a new plugin.
you just then have to rename the files.
To download the basic vvvv dependencies it uses the packet package manager - the bootstrapped executable is also included in the repository - you call it with .paket\paket.bootstrapper.exe then .paket\paket.exe init and finally.paket\paket.exe install
there is also a manual build script included but better use vs to build.
i also made a powershell function which does all that automatically. which you can include in your ps config
afterwards your able to clone new template just by “create-vvvv-template name”
That is pretty awesome, thank you. I managed to build a node with visual studio, yey!
Now I have the question whats the best praxis to rebuild the project and to see immidiate changes in vvvv?
because in the moment i have to close and reopen vvvv to rebuild. also if i set it to debug and attach it as the active process in the debug menu of visual studio, it prompts to leave debugging for the build and then build fails because “process in use”.
Regarding your script, which would be also realy cool to get running:
I found its missing a bracket in the end, then i was able to run it, but it doesnt do anything, also when specifying the folder parameter. But maybe I didn`t get your last sentence right about including to the powershell config. Where can I edit the ps config actually? Also cant find it in the web this answer…
for coding without interrupts you better go for Dynamic Plugins or even better: VL
The only way to semi-automate build and run procedure in VS is to use custom post build action in VS or as is did use external build script which build the dll, shutdown v4, copy the dll, restart vvvv. thats cumbersome in any way. debugging plugins with VS is only possible if you build and run them beside the whole vvvv sdk which is another story - but at least you wouldn’t need to shutdown v4 manually every time…
regarding the script. actually it isn’t one. its just a function which you can paste into your personal psconfig.
you can actually just use vs as ide and debugger, still having vvvv compiling the dynamic plugin and recompile via resetting the node a la alt right click.
for simpler stuff my workflow is creating a dynamic plugin in vvvv as always. not opening the built in editor, but just open the generated csproj via visual studio. do my coding there. everytime i need a rebuild, just save in visual studio, reset the dynamic plugin.
woei seems to take a hybrid approach, telling from his github repos.
the vvvv dlls are sometimes pulled from nuget and referenced from /packages
but usually his stuff is dependent on a certain directory configuration, so the plugin finds the dlls relative to his working directories, like here
so yes, I was wrong, you can actually do plugin dev in vs without constantly restarting vvvv, but it comes at the price of some unfortunate csproj classpath hacking.(or reverse engineering and mimicking the original directory structure of the author)