Performance Improvements in Visual Studio 2008


It seems I’m doing a lot of referral postings this month and I’ve got a couple more for you.

This is the first one, near and dear to my heart because I worked with Cameron on some of these (and he didn’t mention me at all, *sniff*) especially the performance problems in the cases with “Venus” (the ASP.NET project system), and one of my teammates, Hazim Shafi, worked with VB on many of the other issues too.  I’m very happy with what we managed to do, although there’s always more 🙂

Anyway, without further ado, here’s Cameron McColl talking about performance improvements VB made in VS2008.

Comments (4)

  1. Doug says:

    When you have a million line WinForms project a number of things slow down in VS 2005.

    – toolbox takes a long time to load especially when you have a lot of user controls

    – large files can be painfully slow to type within.  Is there an easy way to toggle intellisense on and off?

    There may be better ways to orgranize to avoid the problems with large projects, but it would be nice if VS worked with large projects better.

  2. Mark says:

    Turn off AutoToolboxPopulate in Tools->Options->Windows Forms Designer->Tools.

    It defaults to On.

  3. Russ says:

    What’s the deal w/ these Channel 9 videos? It really frustrates me to have to sit through a 15 minute video to find out what I could have read in under 5 minutes. Not to mention there’s no way to search/index the content. Not to mention audio isn’t always available.

    The time making the video would be much better spent typing up a blog entry. Or at least provide a transcript.

    This probably isn’t the best place for this rant, but I needed to say it somewhere…

  4. Doug says:

    I think that the problem of working on large programs in VS illustrates that techniques that work well on smaller programs do not scale well to larger programs.  This is something that we all face as programmers.

    Writing a little line counter/stats program that reads sln, csproj and cs files shows the scale of the problem.  It takes a long time to read in the files of the large project and compile that stats on it. There must be optimizations that I could do to make it run faster. Seeing how slow my little program runs gives me sympathy for what the VS programmers have accomplished.

    It is still pretty amazing what VS can do and it is worth it even if it is a little slow sometimes.

    If intellisense runs on a background thread, does the pending operation get killed nicely when you move the cursor?