BreakpointManager,BreakpointSite

Hey

i am creating a custom component and want to give the user a breakpoint or 3. in AcceptBreakpointManager I say

this._bpm = BreakpointManager

_bpm.CreateBreakpointTarget(1,"You hit #1");
_bpm.CreateBreakpointTarget(2,"You hit #2");
It was my understanding that I would be able to see these breakpoint descriptions in the list of breakpoints for my custom task. I cannot. All i see is OnCustomEvent which unless I have missed something does not tell me which breakpoint was hit.

In Execute() I check to see if the breakpoint is enabled (checked) and go from there

Did I miss something?

Allan

Allan, this looks right to me. I'm assuming _bmp is valid when you call it? Are you using the breakPointMgr that's getting passed in as a parameter?

K

|||Hey Kirk.

Yeh _bpm is a BreakpointManager at the class level and would seen to be valid. breakpointManager is the value passed in to the method.

Ok So i just figured why it does not work.

I had removed the interface IDTSBreakpointSite from my task. Now i have added this back it works.

Once thing though. In BOL it says that IDTSAcceptBreakpointSite.AcceptBreakpointManager is called by the runtime and not used in code. BOL then goes on to give an example (I have always overriden this method also).

To what does BOL when it says "not used in code" refer?

Thanks Kirk.

Allan

|||"I had removed the interface IDTSBreakpointSite from my task."
Yep, gotta have that or the TaskHost won't forward the calls.

"To what does BOL when it says "not used in code" refer?"
I have no idea what that means. It might mean that the task itself should not call that function, which is true. But, I dunno for sure what, "Not used in code" means.

Breakpoint in child-package triggered on first execution only.

I have a child package which is executed several times within the same SSIS ETL. I have placed a break point on one of the child package's tasks, set to trigger on a PreExecute() event. The first time the child package is invoked, the breakpoint is triggered. However, on each successive invocation the breakpoint is ignored. Does anybody know if this behaviour is normal? Thanks in advance!

This is a known issue and we are aware of the bug. Thanks

Breakpoint doesn't work

I've got a breakpoint in a script task. The script task executes successfully but doesn't break.

Short and sweet this one. Anyone any idea why it might not?

-JamieHey Jamie, I believe I read somewhere in the pipe that breakpoints weren't going to work until the prod release...|||

JAson_scoobyjw wrote:

Hey Jamie, I believe I read somewhere in the pipe that breakpoints weren't going to work until the prod release...

Nah, I know this has worked in the past and I've read posts today from people that have had it working.

-Jamie|||We don't support breakpoints in script data flow component in this release.

The script task breakpoints should work, except when the package is executed using 64-bit runtime on x64 machines.

Jamie - are you using CTP 16? I remember in some older builds the script task breakpoints did not work if the PreCompile property of the task was true. I think it is fixed in CTP 16 (but it could be after CTP 16 - for RTM, not sure).|||

Michael Entin SSIS wrote:

We don't support breakpoints in script data flow component in this release.

The script task breakpoints should work, except when the package is executed using 64-bit runtime on x64 machines.

Jamie - are you using CTP 16? I remember in some older builds the script task breakpoints did not work if the PreCompile property of the task was true. I think it is fixed in CTP 16 (but it could be after CTP 16 - for RTM, not sure).

Hi Michael,
Yeah, I am using Sept CTP/IDW 16 and I do have PreCompile=TRUE.

The package is at the office and I am currently at home so I'll check this out (i.e. set PreCompile=FALSE) on monday.

-Jamie|||http://blogs.conchango.com/jamiethomson/archive/2005/10/15/2271.aspx|||I found that if you are in debug at a breakpoint on a looping bit of code. If you press F5 the code then continues and doesn't break on the break point again, even though the statement with the breakpoint is executed again.

I thought F5 ran the code and if a breakpoint is found it should stop?|||Is it true that breakpoints won't work in a script component?

I just wrote a script source component to reorder the columns in incoming CSV's based on the column names in the first row.

I set some break points to debug, but they get ignored every time I try to run it. My "precompile" flag is set to false per some earlier posts, but that doesn't seem to affect the issue.|||SSIS does not currently support breakpoints in script components.

You will need to put some logging information in your script component see my post http://www.sqljunkies.com/WebLog/simons/archive/2005/08/03/SSIS_Script_Component_Debugging.aspx