Hi,
I didn't play around with breakpoints to much, yet. So today I created a package with 2 variables, which both raise their change event. I added a event handler for that just to show the name of the variable which initiated that event (system::variablename) in a messagebox. I added two scripts to the main workflow, one changes one variable, one the other.
To see what's happening I placed a breakpoint on the script in the event handler. I start the package, the first script is executed, the event is fired and the script is started. The breakpoint stops executing the package. So good so far. When I now click on "continue" the script task in the event handler changes to "yellow" and I hear a beep. That's all. I don't see any other action in the package, the second script is not started and the run seams to be locked.
What's wrong? Is the problem sitting in front of the monitor? Am I the 1000th person hitting that bug?
Thanks,
Thomas,
I've never seen that happen. Mind you I can't remember ever setting breakpoints on something in an eventhandler. Perhaps that could be the problem? I'm only guessing tho.
-Jamie
No comments:
Post a Comment