SSIS Script component hangs while debbuging

Question

I often have to debug my SSIS script components. I often at times accidentally try to edit the script while debugging. An change to the script while debugging causes vista ide to hang and I have to wait a two or three minutes to time out and ask me if I want to close the app.

Is this normal behave. If I simply received a notification that you cannot edit while debugging that would be fine but is hanging, closing, and having open again is very tedious. Ideal world it would let me edit while debugging like in Visual Studio C#.

Also I lose any watch variables set between edit sessions - is there a way to preserve them (export / import).

Thanks

Carl

Answer 1

It is normal behavior for the Visual Studio Tools for Applications (VSTA) to hang or become unresponsive when trying to edit an SSIS script component while debugging. Unfortunately, VSTA does not support live code editing during debugging like Visual Studio does for C# projects.

To make the debugging process less tedious, consider the following:

1. Add breakpoints in your script: This helps you pause the execution at specific points and inspect variable values or step through the code to understand the issue.
2. Use Debug.WriteLine or Console.WriteLine statements: By adding these statements to your script, you can output variable values and messages to the Output window in VSTA or the SSIS logging. This can help you track the execution flow and understand issues without editing the script during debugging.
3. Test your script components in a separate C# project: If the logic in your script component is complex, consider creating a separate C# project to test the code. Once you have verified that the code works as expected, copy it back into the SSIS script component.

It is normal behavior for the Visual Studio Tools for Applications (VSTA) to hang or become unresponsive when trying to edit an SSIS script component while debugging. Unfortunately, VSTA does not support live code editing during debugging like Visual Studio does for C# projects.

To make the debugging process less tedious, consider the following:

1. Add breakpoints in your script: This helps you pause the execution at specific points and inspect variable values or step through the code to understand the issue.
2. Use Debug.WriteLine or Console.WriteLine statements: By adding these statements to your script, you can output variable values and messages to the Output window in VSTA or the SSIS logging. This can help you track the execution flow and understand issues without editing the script during debugging.
3. Test your script components in a separate C# project: If the logic in your script component is complex, consider creating a separate C# project to test the code. Once you have verified that the code works as expected, copy it back into the SSIS script component.