Despite the fact that we made what I still feel is a solid release, we’ve been clearly seeing some customers having problems with the performance of the VB 2005 compiler when used on large VB projects. In response to a number of problems that we’ve isolated, we’ve released a QFE that addresses many of the major problems people are having. To quote the announcement in the forums:
We’ve received feedback, both directly from developers and in the forums, regarding slow performance of the Visual Basic 2005 IDE in certain situations (larger projects, projects with many errors, etc.).
I’m sorry that these issues made it to production and degraded the performance of the IDE. The Visual Basic Performance team is working hard to address these issues via hotfixes and the upcoming Visual Basic 2005 SP1 while we work on engineering changes to make sure that issues such as these never make it into a shipping product in the future.
Based on this feedback and forum posts, we’ve been working with customers to address these performance issues. We recently released a performance hotfix to address the following areas of Visual Basic 2005 performance:
- Improves the performance of single-stepping (F10) debugging.
- Improves the performance of Task/Error List Refresh.
- Improves the performance of Intellisense.
You can learn more about this hotfix in the KB 920805 article (http://support.microsoft.com/kb/920805/en-us). In order to get this hotfix, you need to contact support and reference KB 920805. Details on contacting support can be found at http://support.microsoft.com/contactus/?ws=support.
Note that this hotfix rolls up all performance hotfixes to date, so installing this hotfix will give you the best IDE performance.
Again, we appreciate your feedback and we thank you for your patience while we address these issues. Please contact email@example.com if you continue to see issues after applying this hotfix.
Visual Basic Performance Program Manager
As Chris says, these hotfixes (which you currently have to go through support to get, so we can track the QFEs we’re handing out) will be rolled into SP1. I encourage people to email firstname.lastname@example.org if you are having performance problems that aren’t addressed by the QFE so we can work on isolating the problems you’re seeing and get them fixed.