Installing VS2010 Beta 1

As Somasegar announced this morning, Visual Studio 2010 Beta 1 is now available for download for MSDN subscribers and will be available in a couple of days more broadly. I’m currently installing VS2010 and thought I’d mention a few things that occurred to me during the process.

Customizing the Installation

There seems to be a new screen for customizing the installation process:

vs10-setup

The idea is that you can select if you’re a .NET developer or a C++ developer and continue right away or then click the Customize button and see the old-style customization dialog that was in previous versions.

Maybe it’s just me, but I don’t see the point of this screen at all. Most people I know already customize the VS installation a lot, or will always install it complete, so it’s not like this is actually saving anyone time, is it?

Me? I’ll always go the customization road. For example, I never install Visual Basic; I have little use for it at this time. Oh, and by the way, don’t confuse Visual F# with Visual J# during the installation process :).

While on the subject of customization, anyone know why SQL Server Compact is a required part of the Visual Studio installation? This has been that way for a few years now, and I still have no clue why I’d even want it install; I have yet to use it. Does VS use it itself for anything?

The Installation Process

The actual installation went by without any errors, and was relatively quick (certainly faster than I expected it). You’ll have to restart during the installation just after the .NET Framework 4.0 Beta 1 setup is done.

Unfortunately, I had to go through it twice because I incorrectly installed VC++ instead of VC#!

Something to watch out for: If you decide later to add/remove components, and you didn’t install the Sync Framework initially, it will come up checked by default as soon as you get to the component list screen. So if you didn’t want it, make sure to uncheck it before continuing with the setup.

The Windows SDK

Visual Studio 2010 comes with the Windows SDK 7.0A release (probably a beta build). One interesting thing about the SDK is that the /bin folder of the SDK contains the .NET 3.5 tools, while the new .NET Framework 4.0 SDK tools are contained inside the /bin/NETFX 4.0 Tools subdirectory. So make sure you’re using the right set of tools.

Visual Studio 2010

Launching the IDE for the first time is actually pretty fast; feels very snappy for a lot of things, which is pretty impressive for a beta 1 release.

It does a somewhat reasonable attempt at migrating your Visual Studio 2008 settings, though I noticed that some settings, like the color for line numbers and some of the tool window layouts are not migrated correctly.

The new Text Editor has a nice feel to it, and I rather like the new IDE look. A few comments on it:

vs10_editor

  • Borders/Margins between UI elements are a little on the big side, so there’s actually quite a few pixels of lost space there. If you look at the screenshot on the side, notice particularly that the border between the text editor window and the tool window tabs is actually fairly large.
  • The new WPF-based text editor renders the bold-as-italics in Envy Code R VS pretty badly. And still, several years later and a completely new text editor, and we still don’t have proper italics support. Seriously, people, how many more years do you want us to wait for it?
  • The text editor background color does not appear to be handled correctly. The Fonts & Colors dialog will say that the right background color is selected, but it does not get picked up when you start the IDE, defaulting to White every time.
  • One little nice thing I noticed is that the sample text on the Fonts & Colors dialog is now this:
    vs10_sample_text 
  • There’s a new feature in the editor: If you put the mouse pointer right on the vertical line with the +/- signs for the collapsible text, it will highlight the region of code that would get collapsed by the [-] sign right on top of the pointer:
    vs10_sel
    Unfortunately, there doesn’t appear to be a way to change the background color used for the selection. Or at least I couldn’t find it. I believe this is a side effect of not allowing the user to change the background color for Collapsible Text.
  • Font rendering on the IDE is, of course, very WPFy. Meaning, it’s not great. I think I can live with it on the editor itself (using a dark background seems to help a bit), but the IDE menus look, well, pretty bad:
    vs10_menus
  • The New Project Dialog has some changes. Some are good (and it looks nice, too), but some not as much. The description pane on the right is new, and well, it seems pretty useless to me for 90% of the project templates most people will use. It doesn’t help that the descriptions on the existing templates are pretty simple one-liners:
    vs10_new_proj 
    And by the way, the pane is not resizable at this time.
  • The new Text Editor does not appear to support splitting a code window horizontally, like previous versions did. I sure hope this gets fixed, because it’s a feature I use all the time :(

Conclusion

There is a lot of new stuff on the new IDE to look up, and tons more on the .NET framework. I hope to blog a bit about these in the next few weeks as I dig deeper into all the new stuff.

7 Comments

  1. Damien Guard

    Yeah text rendering is iffy. Should be fixed before final. In the mean time Liberation Mono at 14 looks best.

  2. Noah

    Hey Tomas, thanks for the feedback :) I have a few quick editor-related comments/questions. If you want, you can send the reply to noahric @ microsoft or reply here.

    * With the spacing issue, you’re talking about the spacing between the outside of the editor and the collapsed tool windows, right (i.e. not space inside the editor)?
    * I can send an email about the Envy font rendering to the WPF team – can you write something up about what you expect it to look like and how it’s being rendered incorrectly, so I can give it to them?
    * The background color bug is known, sorry :( You can work around it by opening Tools->Options and clicking OK; it’s annoying I know
    * (Configuring the outlining margin mouseover)
    * You can still split the editor, by either the menu (Window->Split) or by binding a keyboard shortcut to to Window.Split (in Tools->Options->Keyboard). The little margin doohicky that you could be able to drag isn’t there in beta1, though.

  3. Tomas Restrepo

    Hi Noah, thanks for the comments! Re:

    * Spacing: Yes, I mean between the text editor window and the collapsed tool windows. I’m guessing there’s at least 4 usable pixels there :) Actually, more than the wasted spaced is that it just looks a bit weird.

    * Envy Code R rendering: The biggest problem is the italics. As you may be aware (or not), Damien’s font basically tricks VS into rendering items with bold selected in italics instead of real bold. That works great on previous VS builds, but on the WPF editor it looks bad, like hinting is not properly done on the fonts or something.

    I’m not sure if this is a problem with rendering italics in general or just related to the trick that Envy Code R VS does. Anyway, here’s how it usually looks in previous versions: http://www.flickr.com/photos/tomasr/1816308249/in/set-72157602839725762/

    What we really, really need is proper italics support in the editor, but I’m not very hopeful about that.

    * Glad to know about the window splitting! I use that all the time! We do really need to have that be more discoverable though. (And while at it, how about we get vertical splitting? That’s another one I’m always wishing for)

  4. Tomas Restrepo

    Realized that we can get something close to vertical splitting using Window -> New Window and then moving one of the windows to another vertical tab group. Again, needs to be easier, more discoverable.

  5. Tim Wagner

    VS Beta 1 can split a window horizontally (Window -> Split) inside the editor. You can also open multiple copies of most editors (Window -> New Window) and then dock them next to each other horizontally or vertically using the menu or the docking UI. (VB and WebApps are notable exceptions to the latter and can only be split using the former approach.) Both types of splitting can be repeated to create “trees” of split windows. I’d be very interested to know if there are other use cases that you’re looking for that we aren’t covering here.

    W.r.t. the font rendering, you may want to check out Jason Zander’s VS blog; it’s been a much discussed topic since the CTP, so I won’t attempt to repeat it all here. However, I don’t understand the point about italics not working correctly, and would like to hear more about what you see as the problem there and how we could fix it; we’re just using standard WPF text display primitives in our editor.

    The installation comments echo those of others, so that’s likely to change for beta 2.

    Thanks for the feedback — it’s much appreciated.

    Tim Wagner
    VS Platform Dev Manager

  6. Pingback: Winterdom » Blog Archive » Italics Rendering in VS2010 Beta 1

  7. Tomas Restrepo

    Tim: Thanks for that. I figured out about the Window -> New Window thing later on, and certainly there could be some improvements there (I’ve logged a suggestion in Connect about that).

    Font rendering, well, the italics just look worse compared to how VS2008 rendered them (even if you had to hack around to get it displayed). I’ve just posted a new entry with side-by-side screenshots of the same text so you can see the difference.

  8. Pingback: 5 Articulos sobre VS2010 | Coded Style

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>