Debugger won't step from procedure into trigger

[james.artisan]

I've just downloaded the evaluation version of MySQL dbForge. The debugger looks awesome except that I can't get it to work.

I've been working through the instructions found here: http://www.devart.com/dbforge/mysql/stu ... index.html

I have a procedure set up that runs an insert statement which causes a trigger to fire after insert.

It's all good up until step 8 in the instructions (Step through the [procedure] code using the F11 key or the Step Into button, or press Ctrl+F5 to move directly to the breakpoint. At the INSERT INTO schedule_list statement, when you press F11 again, you will step into the trigger.)

The problem is that it doesn't step into the trigger. It fires the trigger. I know it's firing because I get a javascript alert message saying "column 'my_var' cannot be null" which goes away if I comment out the body of the trigger.

I have set break points at the insert statement that fires the trigger, and also have several breakpoints in the trigger code.

Also, as soon as I click "Start Debugging", all the breakpoints in the trigger go white with a little cross icon on them, but the breakpoints in the procedure code stay full red. I don't know what this means.

Can anyone here help me out and tell me how to get the debugger to step into the trigger so I can debug it?

Thanks

[alexa]

Please try to right-click the trigger in Database Explorer and select 'Debug -> Compile for Debugging' from the popup menu before you start debugging.

[james.artisan]

Both the trigger and also the procedure have been "successfully compiled with debug info".

[james.artisan]

Okay, my bad, I had .NET Client Profile installed but not .NET Extended. It is now stepping from the procedure into the trigger.

[alexa]

Please let us know if any questions arise.