Reflecting your feedback in Visual Studio 2019



We started sharing Visual Studio 2019 Previews with the goal to deliver the best possible experience through a more open dialog.

Over the last few months, we’ve seen lots of thoughtful and passionate discussion throughout the community, on the blog, in Developer Community, and a bunch of social media sites. Through these previews, we were able to share some of the UI changes in this release.

We want to say thank you for sharing this feedback. Everyone working on the team has read through all the comments and we’ve done our best to respond to the different themes discussed in the threads.

Hopefully, by now you’ve had a chance to try the Visual Studio 2019 Preview. If not, we encourage you to try out some of the new experiences. There were a few popular themes in the feedback that we wanted to acknowledge and talk a bit about the changes we’ve already made based on your feedback.

Combining the title and menu bar

With the combined menu and title bar, we took an opportunity to give back valuable vertical space and update the layout of the upper shell controls. This also makes the new more accurate VS Search more discoverable and accessible. While we strived to do this without impacting your workflow many users highlighted the title bar was home to several information elements including solution name, administrator mode, experimental instance tag, and the preview badge the were important for navigating between multiple instances of Visual Studio running at the same time.

When we first combined the title and menu bar, we were careful not to remove the solution name from the app title that appears when you ALT+TAB or hover over the app icon in the start menu. We found in controlled studies testing these were the most commonly used elements for establishing context across instances of Visual Studio. As we started to test the changes internally though, feedback surfaced that users still found the missing solution name jarring so we started working on some potential solutions.

We heard another piece of feedback from the community that we’d heard in our studies; users often need more context than just the solution name. Having seen this feedback before in some of our studies we experimented in Preview 1 & 2 with a new home for solution name in the status bar next to the existing branch switcher. While this design had the benefit of bringing solution and repo information closer together it wasn’t very discoverable and didn’t work well with cascaded windows. Preview 3 now brings back the solution name into the combined title & menu bar and updates surrounding controls to reserve space for the name.

The Preview 3 title bar with the solution name as well as instance and preview tags

The title bar included other information in addition to the solution name. We took steps to preserve the other contexts that were previously available in the title bar including Administrator mode, experimental instance, and preview channel by displaying them in a badge under the window state controls. The “Send feedback” and “Live Share” controls are available on the toolbar row while the notification icon has a new home in the bottom right of the shell to better align with common notification patterns.

Blue theme changes

Another goal for Visual Studio 2019 was to make it easy to tell the difference when you have different versions of the IDE open, be that 2012, 2017 or 2019. We refreshed the blue theme, which we’d not touched since 2012, to indicate this step into the future.

What we found through the feedback is that some functional elements from the original Blue theme were lost with the first iteration of the theme update. While most of you generally liked the new theme some customers gave us feedback that it removed some spatial definitions in the UI that helped navigate around the IDE quickly and intuitively. Comments also pointed out that the blue theme updates had gotten too bright adding eye strain over longer periods.

The changes in the blue theme from 2017 to 2019 as well as changes to the title bar, which increases the vertical height available.

For Preview 3, We’ve heightened overall contrast which in turn helped improve legibility, accessibility, and wayfinding throughout the IDE. We reduced the brightness of the base color and added a set of complementary and analogous accent colors. These changes preserve an at a glance difference between versions while tackling the functional feedback.

New Icons

While not the most glamourous part of a new release, the new product icon is an important way to identify our IDE in a busy taskbar, start menu or desktop. It’s also another way that you can tell the difference between versions of our product. In our original post we explained the approach we’ve taken to simplify the icon for Visual Studio as well as create a system for showing the difference between a Preview and full released version.

Visual Studio for Mac 2017 (left) Visual Studio for Mac 2019 Preview (Middle) Visual Studio for Mac 2019 (Right)

We’ve now applied this approach to the Visual Studio for Mac icon which is available to download from our website. One of the challenges with the icon for Visual Studio for Mac was how to create an icon that was closely tied to the Visual Studio Family line of products but that stood apart from the Windows version of Visual Studio so as not to confuse you into thinking they’re the same (just on different platforms). We experimented with many ways of showing a differentiation between the two applications but settled on tying them together as a family, with a background shape that echoes the form of the Infinity Loop, and adds a macOS flavor to the icon.

Let’s continue the conversation

We are truly grateful for all the feedback we’ve received so far and hope to use this to continue to improve the experiences we’re delivering throughout the product. As you find bugs or have suggestions the Developer Community site is the place to log these items for the team to review and the benefit of the community. We’re eager to continue the discussion as you continue to use Visual Studio 2019.


Comments are closed.

  • Avatar
    Eric Richards

    The only thing I really want is an end to the 32-bit memory limit barrier.  I would love to have a Visual Studio that can actually make full use of all the resources on my system, and not splutter and start page-thrashing on large solutions.

  • Avatar
    Laszlo L

    Are you kidding us?
    May I ask how many ‘software engineers’ are currently busy in Redmond tinkering #RRGGBB color hex codes and pixel shuffling in a 16×16 icon? I understand there are still some untried combinations left (and so will be lots of work for you until Visual Studio 2519), but could you please focus on more important things we are really missing.

  • Colin Anderson
    Colin Anderson

    Here’s some feedback: stop wasting time messing around with superficial things like colours, icons and pixels, and actually implement some of the features many users have been begging for for *years*!
    A few examples:
    – Start listening to users (the time-wasting nonsense proudly presented in this blog post is the perfect example of how you are *not* listening)
    – Visual Studio as a 64-bit process
    – Stop wasting CPU cycles when I’m not even doing anything in the IDE (this is the reason I recently switched to Rider – what a breath of fresh air not having my fans whining all the time!)
    – Kill the lag when opening the ‘find in files’ box (this is a long standing bug that’s worked around by messing with proxy settings – this bug has been present since something like VS 2012!)
    – Fix the bug where the project doesn’t start if you click in a DLL project while building an executable project (another bug that has been present for *years*)
    – Improve the *abysmal* performance of the XAML editor
    – Better Roslyn analysers OOTB (R# is practically a prequisite to make VS usable, even though it also damages performance)
    – Local history tracking, with an undo function that works even if you close and re-open a document (Rider has this – it’s *wonderful*)
    – Better F# support. You treat the abomination that is VB.NET as a 1st-class citizen, so it’s high-time that F# was too

    • Avatar
      Lajos Marton

      Totally agree, plus the big not free Visual Studio is completly unusable for real modern javascript development. What is a shame. I have to use VS Code for writing react/vue es6/7 javascript codes and need VS 2017 for running and debugging C# backend. Is this normal in 2019 for an MS developer? While VS 2017 is so bad for a lot of money, then the main issue is titlebar and conversion about new icons? Hahahahaha…..

    • Avatar
      Jamie Young

      Hey Colin, this post was intended to just be the continuation of the conversation we started on UI/UX changes coming to Visual Studio 2019. However I think the title of the post has been misleading (in that it indicates it covers everything that’s going on, not just the UX/UI work) so apologies for that. I think all of those issues you’ve raised sound like things we should be tracking in our Developer Community site. If you’ve not already, please raise tickets against them. If tickets are there, please upvote them so they get to the right people fast. Sorry to hear you’re so frustrated and we’d love to tempt you back from Rider but sounds like we’ve some work to do until we can. This sort of feedback is exactly what the team likes to hear, thanks for taking the time to give it.

  • Avatar
    Serge Lussier

    Merging title bar with the menu and hopefully, other widgets is a very welcome “space optimization”!! At last! Old annoying space wasting title bar was so …..1990!! One line of code more visible can mean a lot.
    [EDIT] I am 53 years old and an old geyser c/c++ coder since 1988. Thus I know what I am talking about. I ALWAYS hated that ugly waste of empty space that we call “title/drag bar” !!! [END EDIT]

  • Avatar
    Richard Moore

    Icons schmicons 😉 What I’m most interested in is what (if anything) has been deprectaed. For instance VS2017 ditched the ability to “Update Service Reference” which means we have to still revert to VS2015 for certain operations. And I second the request to get VS fully 64 bit.

  • Avatar
    Chuck Ryan

    Ok the joke is over, pretty funny actually but a little bit of a reach trying to make everyone think you spent all this time on removing the title bar and changing a theme color, so what have you guys actually been working on?

  • Avatar
    Data Juggler

    How is the News channel viewed in 2019? You do realize if it weren’t for the News Channel on the start page, I wouldn’t have read this blog post or known about any upcoming Microsoft event like April 2 VS 2019 launch.News is my only access to what is happening in the outside world other than Google. Please return News to the new start page or provide an extension that does this, else I won’t know about VS 2021? 

  • Avatar
    Tony Henrique

    I liked the Combining the title and menu bar, but I noticed a detail: If you try to move the window by clicking over the Title text, it does not move the window, and I think that it should move the window if we drag the Title text.