Routine crashing of Visual Studio 2005 when running or editing SSIS

We have found that it is common for Visual Studio 2005 to crash when editing or running SSIS packages -- from CTP versions through beta versions and including the release version.

Of course we kept hoping that newer releases would become more stable, or at least more robust -- and now I'm hoping there will be a service pack, which might make it more robust?Can you repro the crashes, have you submitted the bug report?|||Please consider this the bug report then -- this is all I know -- it very often crashes.

We have never observed any correlation to any action in particular, or even to any particular development machine or package.

So there isn't anything obvious for me to even try to reproduce them at a desired time. So I cannot really make any useful bug report -- at least, as a programmer, I think a bug report isn't too useful until it either is reproducible or at the very least is correlated to something.

It just tends to to crash -- well, ok, a common point (but not too helpful I guess) is that all the machines involved use Windows Server 2003, and some version of SQL Server 2005 -- now they all use SQL Server 2005 release or SQL Server 2005 SP1, as all have either been upgraded to release or reinstalled with release -- we no longer use any CTP or beta versions.

Another common point is they mostly use the same set of databases.

Oh, and most are x32 versions, except one is an x64 version of Windows Server 2003 SP1.

On some forum somewhere, someone pointed me to some beta newsgroups and asked me to submit some of my many SSIS bug reports to it, but I spent some time trying to access it, and went through the usual connectivity problems involved with hotmail or passport, and never could get access. I posted my bugs, and my descriptions of how I could not access the site to file them then, and didn't get any followups, so I didn't see anything else to do with them.

I never found any simple working system to submit bugs, except to post them to SSIS forums I could find, so I just did that, in hopes they'd help someone at Microsoft who saw them. But, those bug reports at least had descriptive & often proscriptive info -- here, I don't even have that.

I was kind of hoping that an upgrade to SSIS would come along that would fix a lot of the crashes, and hopefully also fix the parameter parsing problems in SSIS -- apparently the msdn help is still not updated to reflect how OLEDB parameter parsing in the ExecuteSQL control flow task really works?|||bug reports may be submitted at the sql server feedback page: http://connect.microsoft.com/feedback/default.aspx?SiteID=68