Inside Visual Studio Beta 2 – Performance and Reliability

After my keynote speech yesterday at the Development Tools Ecosystem Summit Charles Torre caught up with me and we made this video.  Hot off the presses: Rico Mariani: Inside Visual Studio Beta 2 - Performance and Reliability

It's super-exciting 🙂

If you missed the keynote you can get virtually all the content by watching this video and reading the last entry in my History of Visual Studio series My History of Visual Studio (Part 10, final).


Comments (8)

  1. Peter says:

    Just installed B2 and noticed the speed being much improved, nice job! Also the text rendering is how it’s supposed to be (i.e. pixel aligned), a big thank you!!

    I personally don’t like Consolas, especially when you turn off ClearType, so in all places where Consolas is used I replace it with something else (Courier New or Tahoma). The only place I couldn’t find how to change is the IntelliSense box (for the designer’s code view). I went through all the settings under Environment -> Fonts and Colors and none of them show Consolas, but the IntelliSense box still uses it. This is only for the IntelliSense in the designer (code view). It displays the right font in code (.cs), so I’m assuming this is a bug. Other than this and occasional dot leftover from the cursor (could be because of the font I’m using — Courier New) everything looks great. Keep it up!!

  2. Peter says:

    A few more things 🙂

    I really like how you can drag out any window to a different monitor — awesome feature. What would make it even nicer if we could dock several windows together. Similar to how you can group windows in Chrome.

    A small feature that would be nice is to be able to add commands to the actual menu bar at the top. In VS2008 and prior you can do this. The idea is to place some often used command right on the menu bar, next to "Help". I usually place Run/Stop and "Close All Windows" there. It’s not terribly important though 🙂


  3. Peter, if I understand you correctly, you can still do this.  I’m using VS 2010 Ultimate:

    1. Right-click on the top-level menu bar

    2. Scroll allll the way down and select "Customize…"

    3. Switch to the "Commands" tab

    4. Select the "Menu bar" radio button and "Menu Bar’ dropdown option

    5. Click "Add Command…", choose the command you want to add, click "OK"

    6. Click "Move Up"/"Move Down" to position the command

    7. Click "Close"

    The command should be there on the top-level menu bar.

  4. Peter says:

    @Chris: Thanks! In VS2008 I could drag and drop commands and since that didn’t work I didn’t try any other way. So yes, that works (differently) so scratch that.

  5. Miral says:

    I haven’t tried the beta yet, so I can’t speak from experience with it, but certainly in VS2008 and earlier you could dock tool windows to each other as well as to the main window (eg. making a big "second-monitor" window divided up into subwindows)…

    (I’d be somewhat disappointed if this ability has been lost in VS2010.  Only somewhat, because I end up switching to single-monitor setups often enough that I tend to use pinned auto-hide windows now rather than trying to have everything visible on a second monitor.)

  6. Ryan Molden [MSFT] says:

    The ability to doc toolwindows is still present, he is talking about docking free-floating document windows, which wasn’t possible (floating document windows) in 2008 and we didn’t implement ‘rafting’ (as it is called) in 2010 for document windows (but rafting is still possible for floating toolwindows and adding floating documents to existing toolwindow ‘rafts’).

  7. Ryan Molden [MSFT] says:


    Yes we didn’t have the time/resourcing to do drag&drop customization of the command UI like we had in Orcas so we only support the Customize dialog method 2010.

  8. Brad says:

    That video with Charles is really interesting!

    Is there any chance you will write up your procedures for profiling and improving WPF performance? I’ve read the material on msdn, but figuring out how to tweak things to get faster rendering can be quite tricky (and figuring out when things like data binding are slowing responsiveness isn’t to easy either). Just a thought, since tools like profiling don’t always seem to be the easiest to apply to UI responsiveness problems.

Skip to main content