A Big Fix

Question

A Big Fix

Steve Jones - SSC Editor

SSC Guru

Points: 736212
More actions
August 15, 2006 at 3:28 pm

#191946

A Big Fix
I heard about this fix for the Visual Basic 2005 IDE from a number of sources. Apparently the IDE has some issues with large projects and works sluggishly. From the performance I've seen in small projects, I guess if you ever close and then open the IDE, you're rather annoyed about the overall performance enough without seeing degradation from a larger project.
All last year I was closely following the final work on both SQL Server and Visual Studio and it seemed that the SQL part of things was moving quicker than the VS2005 area. But they were fairly intertwined, so changes in one side often forced some changes, or substantial testing in the other product.
I don't have any large projects to test this on, but I hope that it was an intelligent, well engineered fix and not a hack. I know there's pressure to get the fixes out quickly, but having to fix a fix later isn't what builds confidence in the product.
If you've having issues, I urge you to check out the KB article and get the hotfix.
Steve Jones

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

William Plummer SSC Eights! Points: 803 More actions · Answer 1

Most of my career I did not have the luxury of deciding when to upgrade development tools. However, that has changed with this job and though I love all the new bells and whistles of VS2005 versus VS2003 I purposely decided to wait a while before using VS2005.

The article states that it is only a problem in specific cases, but it makes my decision to wait a little more justified.

I do plan to develop my next "big" project in VS2005. I think most of the bugs have been fixed. I hope...

Frank Buchan Default port Points: 1405 More actions · Answer 2

When pundits say that Beta 2 of VS 2005 seemed more bug-free in some regards than the release, they are being honest. As someone who tested the product from an early stage, and has developed within it, I have found myself sadly recommending people stick to either very small one-off projects with it presently, or go with VS 2003. The IDE is unpredictable, slow in many places, and prone to strange stops and starts. Combine that with the radical changes to some task-processes in the interface, and you end up with a problematic learning curve at times.

The fact wehave not seen a service release for it yet is indicative of how deep the troubles run, I suspect.

lionfan91 SSCrazy Eights Points: 8794 More actions · Answer 3

I am developing a VB.NET 2.0 WinForms application. My solution has 8 separate projects and over 220 total .vb files. I ran into the problem described in the KB, got the hotfix, and the IDE doesn't crash anymore. The editor is still slower than I'd like, but it's workable. Anxiously looking forward to the service pack though...

Dan L. SSC Veteran Points: 217 More actions · Answer 4

I had this issue with a VB project with over 1,000,000 lines of code! It was so SLOW!!!

After the patch - WOW - I can actually scroll down my project list without it freezing constantly (though it still happens RARELY).

Timothy-313907 Ten Centuries Points: 1226 More actions · Answer 5

I don't use VB, rather C#, so I've never experienced the problems mentioned in the KB but Visual Studio 2005 as a whole is just slow, it's not just with the VB editor. I have a 2.2 GHz machine with 512 MB of RAM and I feel like I have a Pentium 3 1 GHz or something while using VS 2005, it's like swimming in molasses. But since I really like the features of .NET 2.0 I'm willing to trudge along with it. I am anxiously awaiting a service pack!