To be honest, debugging is kind of a pain in the ass too. You have to perform these steps:
[list:58kh1iia][*:58kh1iia]Batch build debug and debug runtime.[/*:58kh1iia]
[*:58kh1iia]Move them into the Construct directory.[/*:58kh1iia]
[*:58kh1iia]Boot up Construct.[/*:58kh1iia]
[*:58kh1iia]Build a test program cap using the new plugin, so that Temp.exe is updated.[/*:58kh1iia]
[*:58kh1iia]Finally, set your IDE to debug with Temp.exe and run it.[/*:58kh1iia][/list:u:58kh1iia]
Sometimes this doesn't even work for some reason, but this seems to be the only way to do it. Every time you make a minor change to the code, while debugging, you have to perform these steps. So yeah save yourself the trouble and run in release and runtime unless you absolutely have to debug. Debug also runs slower, which for most plugins will be an unnoticable difference unless they are processor intensive. I noticed a slowdown with GridTree running in debug.