2012年3月25日星期日

Anyone here know how to work around the persistent long lines bug?

There is a problem that was at least in the February CTP and the April CTP, that a package will enter a state of being slow to open and always put up a message box saying
(the message box does not allow copying the text, or I would post it verbatim, but it is something about extremely long lines of text, and that the product will run slowly)

I've asked in the newsgroups if there is a file that I could edit, manually inserting carriage returns to try to hack around this bug, but never got an answer there, so I thought I'd try here. (Actually, I think I was told that the bug was fixed, but it has persisted here into the April CTP.)
Does anyone here know a way to fix or hack around this bug, or have tried editing some file (dtsx, dtproj, sln, suo, I don't know) to fix it?

Microsoft Visual Basic 2005 55603-000-0000016-00403
Microsoft Visual Basic 2005
Microsoft Visual C# 2005 55603-000-0000016-00403
Microsoft Visual C# 2005
Microsoft Visual C++ 2005 55603-000-0000016-00403
Microsoft Visual C++ 2005
Microsoft Visual J# 2005 55603-000-0000016-00403
Microsoft Visual J# 2005
Microsoft Visual Studio Tools for Office 55603-000-0000016-00403
Microsoft Visual Studio Tools for the Microsoft Office System
Microsoft Visual Web Developer 2005 55603-000-0000016-00403
Microsoft Visual Web Developer 2005
Microsoft SQL Server Analysis Services Designer
Microsoft SQL Server Analysis Services Designer
Version 9.00.1116.00
Microsoft SQL Server Integration Services Designer
Microsoft SQL Server Integration Services Designer
Version 9.00.1116.00
Microsoft SQL Server Report Designer
Microsoft SQL Server Report Designer
Version 9.00.1116.00
Microsoft SQL Server Report Model Designer
Microsoft SQL Server Report Model Designer
Version 9.00.1116.00

Hi Perry,

You are right; this problem should be fixed in the latest builds (June CTP). The file that complained about long lines is dtsx file. I would not recommend going in and inserting new lines in this file, it could create a bigger mess.

The best thing for fixing it would be to install June CTP build, load the package and save it again using the new build.
Thanks,

没有评论:

发表评论