I discussed a little while back that we’ve made a few hotfixes available to address some performance issues people have seen with VB. There’s now a program that makes these hotfixes available as a regular download, rather than forcing you to call support. I’d recommend anyone running into performance problems give them a try…
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 firstname.lastname@example.org 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 email@example.com 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.
In addition to my interview with the ITPro website, I’ve also got a personal webpage on MSDN Japan. It has links to things like an interview I did with Takashi Tsujigo, an evangelist from MSDN Japan, and an interview with @IT. I believe there are also going to be some webcasts up before long. Unfortunately, I don’t believe there are any English translations available for any of the content, although I don’t think I said anything secret that I haven’t said elsewhere… <g>
OK, well, now that I’ve had a chance to recover a bit from the jet-lag from flying back and forth from Tokyo in just three days, I thought I’d give a short update on how the launch went there.
Executive summary: Great!
This was my first experience presenting outside of the US, and it was very interesting. My main presentation on VB 2005 was simultaneously translated, but everything else was done sequentially. So I spent a lot of time saying one or two sentences, pausing, saying one or two more sentences, pausing, saying one or two more sentences, listening to the reply in Japanese, waiting, then hearing it in English. Rinse, repeat. The translators that I worked with were great, so it wasn’t difficult or anything, just a little… different. I did my PDC presentation for a small group of people and it took about twice as long as the original did. I’m also not sure how much of what I was saying got across — all the technical stuff did, for sure, but I think so much of the inflection and all gets, you know, lost in translation.
The special keynote that I did for VB 2005 seemed to go over well, although the fact that the audience was much more reticent that I was used to was a bit disconcerting at times. At first when I wasn’t getting any applause when demoing some of the cool VB 2005 stuff, I started to panic that I was doing something wrong, but then it smoothed itself out. Everyone seemed very excited and had lots of questions about the new version, VB6 migration, the future, etc. Overall, a wonderful experience!
My main regret was that I had to leave right after the conference was over… it would have been great to have been able to spend some time in Japan getting to see something more than the hotel I was staying in. Alas, the confluence of the conference and the impending Thanksgiving holiday made that impractical. Thankfully, I did get a chance to hang out a bit with Cameron Beccario, which was a treat. I tried to convince him to come back and help us out with LINQ, but he’s still pretty settled in Tokyo, unfortunately…
If you read Japanese, feel free to check out my special MSDN website that they put up for me. I’d also highly recommend the VS User Group (VSUG) website — I got a chance to talk with their founding members, and it looks like a great organization! (They said that usually user groups start in the US and then create a Japanese chapter — this time they’re starting the group in Japan, but are open to having a US chapter join. <g>) All in all, a great trip!
We’ve now got the final version of the Visual Basic 8.0 Language Specification now up and available on MSDN! And, as it seems with everything these days, I’ve already gotten several bug reports for the samples.
Updated 11/26/05: Corrected link to language specification. (Thanks Roger!)