Script Component – “extremely long lines of text”

In all my SSIS packages where I have created a Script Component (destination) in my Data Flow and set the PreCompile option to True; the binary of the script is being put in the dtsx fileas a single line. Subsequently every time I try to open the package, Visual Studio warns me that: “Document contains one or more extremely long lines of text. These lines will cause the editor to respond slowly when you open the file. Do you still wish to open the file?”

Any idea how to fix this?

NOTE: This does not happen for any PreCompiled Script Tasks. For these the binary is broken into multiple lines in the dtsx file.

Thank you for your help,

-Tim

Tim,

Unfortunately this is a hangover from using the VS shell. There's nothing you can do about it.

-Jamie

|||Oddly enough, this bug is listed as "fixed" with a note from an SSIS team:

Resolved as Fixed by Microsoft on 2005-10-18 at 16:20:03
Thanks for your report, we're getting this message removed in a service pack.

Best regards,
Sergei Ivanov
Integration Services Development Team Resolved as Fixed by Microsoft on 2005-11-17 at 12:25:30
Thanks, this is fixed.

Sergei Ivanov
Integration Services Development Team

You can see the full bug report here on the MSDN Product Feedback Ctr. It's BUG ID: FDBK37397.
However, the KB Article for SP1 (KB913090) detailing the fixes seems to make no mention of it, at least none that I could find in a quick passthru. When I can find a machine to test the SP1 CTP, we'll see.
|||

Yes, this is fixed by SP1. AFAIK the KB is not the complete list of fixes.
There is a limitation with the fix though: you need to create new script component with SP1 build of SSIS. The script components created with RTM build still have this issue (this is done so that the precompiled script of these components can be read by RTM build of SSIS, otherwise we would break backward compatibility).

By the way, you don't need SP1 CTP, the final SP1 has been released.

|||I have a package with no script components yet I still get this error message each time I load it. Here is what I have discovered. When I set the ProtectionLevel property to EncryptAllWithPassword I get the error message. When I set the ProtectionLevel to EncryptSensitiveWithPassword the message no longer appears. Any Ideas why?|||

dgrm44 wrote:

I have a package with no script components yet I still get this error message each time I load it. Here is what I have discovered. When I set the ProtectionLevel property to EncryptAllWithPassword I get the error message. When I set the ProtectionLevel to EncryptSensitiveWithPassword the message no longer appears. Any Ideas why?

I would guess that the encrypted results in some rather long lines. AcryptAllWithPassword will result in more encryprion than EncryptSensitiveWithPassword.

Take a look at the contents of the .dtsx file and see if it becomes obviousl I would also guess that the size of the file differs quite a bit as well.

-Jamie