ssis-Mode Script Component

Scripting SSIS is more powerful than the DTS log schema, and you don't need to write a msgboxes to get the log information you need.

Because your script component is inherited from a scriptcomponent component with a log method, this method allows you to return a message to the SSIS package's log, which triggers a scriptcomponentlogentry call, such as the following code
(VB code)
Dim x (0) as Byte
Me.Log ("Hello", 0, X)

To catch this event. You must allow log events to be set in the Siss log settings

But the annoying thing is that you have to set this up for each task instead of inheriting it directly from the package, and if you hate it, you can use the following methods.

You can configure what types of events can be triggered at the package level, such as messages, progress, warnings, errors, etc.
The following code:
Me.ComponentMetaData.FireInformation (0, "Simons Task", "Some message to return", "", 0, True)

So once you allow the OnInformation event to be logged at the package level, the information generated by the above statement will be arrested and caught

To easily see the event information at run time, you can display the Log Event window (SSIS menu, logevents option)

Finally, you can still use msgboxes as a breakpoint if you want to