» Debug vvvv plugins using visual studio 2005
This site relies heavily on Javascript. You should enable it if you want the full experience. Learn more.

Debug vvvv plugins using visual studio 2005

This document shows how to use visual studio 2005 to debug plugins within vvvv itself, instead of using the Plugin Hoster.

Create a new configuration

In order to be able to debug our plug-in from within vvvv, we need to set the build path to the Plugins folder.

Go to Build -> Configuration Manager

</img>

Within the Active configuration drop down, select : "<New...>"

Choose a name for your configuration (For example: vvvv-debug), and select "Debug" in the copy setting from drop down. Leave the check box checked.

This allows us to keep our old configuration when we want to do test builds, and swap to vvvv-debug when we ready for testing.

Now we need to setup our path to be able to deploy our plug-in in the vvvv folder.

Right click on your project, then choose "Properties".

Go to the "build" section, and then choose your configuration.
On the "output path" section, choose the vvvv plug-in folder.

To avoid having duplicate libraries, I also recommend to setup the Utils and PluginInterfaces references “copy local” properties to "false".

Attach visual studio debugger to vvvv process

Now your configuration is ready, we will debug our project.
Put a couple of breakpoints in your plugin, and build you plugin with the configuration above.
(Note: make sure vvvv is closed before building, otherwise it will fail).

Run vvvv.
Go to "Debug" --> Attach to process

Choose "vvvv.exe" in the list, and then click on "Attach".

The debugger will start by itself. If you add your plug-in within the vvvv patch, you should be able to follow step by step what it does now :)

Auto start vvvv when we start the debugger.

To simplify our life, we will make visual studio start vvvv automatically when we start the debugger.
We go back to our project properties
Go to the debug section.
On the "Start Action" choice, choose: "Start Program".
Then browse to have the vvvv.exe file in the box.

Now when you will press the Start Debugging button, Visual studio will start vvvv and attach itself to the process.

When your stop the debugger, vvvv will also stop by itself.

by vux

anonymous user login

Shoutbox

~9d ago

fleg: This Tuesday, Cologne: exhibition opening of "interwoven", textile disinformation patterns created with vvvv. https://fleg.de/news/exhibition-interwoven

~22d ago

manuelgonzalvez: Assimp nodes all broken afted Win Update w/exception "COM object that has been separated from its underlying RCW(...)"

~22d ago

manuelgonzalvez: @levi thanks would love to! anyway managed to get something similar working based on forum search and anthokio's patches.

~23d ago

levi: @ravasquez thanks. 31.2 x86 verrion worked. @manuelgonzalvez i have a dx11 projectTexture if u a want.

~24d ago

manuelgonzalvez: Anyone has a dx11 port of "projectedTexture" dx9 fx for projection mapping?

~24d ago

manuelgonzalvez: Anyone has a dx11 port of "projectedTexture" dx9 fx for projection mapping?

~25d ago

ravazquez: @levi not sure bout the ImagePack, but I believe VL.OpenCV should give you the same tools and should work with beta just fine

~25d ago

levi: anyone knows of a VVVVpacks.image that works for elliot's projector calibration patches?x64,dx11. always crashes v4 on solve.

~1mth ago

Lorenz: VJing with GIFS: https://lorenzpotthast.de/gifjockey/ A fun little side project, that I first prototyped in v4 and now turned web-based ;)

~2mth ago

schlonzo: finally fixed in 4.8 nice1