Answer 1

From my little experience, breakpoints inside data  flows (script components or not, but specially script  components) don't work.

Use System.Diagnostics.Trace, run the package with DTExec.exe and see the output in DebugView.

Answer 2

Paulo is correct - script  components can't be debugged with breakpoints, allegedly due to the threading involved in the pipeline.

I prefer using ComponentMetaData.FireInformation instead of the calls from the Diagnostics namespace.

Answer 3

It seems to me that none of my break  point are working..which is separate issue, but yet making the one above more complicate.

Is not catching Break point  in the Script Component is known issue.

Answer 4

Just be aware that, although it doesn't set  your package in fire, it does fire the OnInformation event that will be propagated up to the top level package (unless you explicitly tell it not to).

But that's the sure way to get runtime info in Visual Studio's ouput window.

Answer 5

None of your breakpoints in a script  component will work.  That's the definition  of "you can't use breakpoints in a script component."  They're not supported.  It's a known issue.  You can't use them.  Don't try.

Use FireInformation, or MessageBox.Show instead.

Answer 6

Thanks Paulo and Todd.

I used MessageBox.Show for now ,

I am going to explore more on System.Diagnostics.Trace

cause when I am processing thousands of record and multiple column per row, catching bad  data is vry tedious and time consuming.

Answer 7