Back in May, we showed a first look into the UI Refresh that we’ve been working on for Visual Studio. We’ve been working on a refresh for the Visual Studio UI to improve productivity, create a more inclusive environment, and keep up with evolving global accessibility requirements. The feedback we’ve collected from that first post and the developer community ticket has been wonderful. We’ve been spending the time since then working through all your comments to ensure your valuable feedback gets weaved into the UI Refresh. Now, here at Ignite, we’re excited to finally make a version of the UI Refresh available for folks to try for themselves.
To enable the UI Refresh, first go to Tools > Manage Preview Features from the main menu in Visual Studio. Then, look for “Experimental control styles”. Once that box is checked, you’ll need to restart Visual Studio for the UI Refresh to be enabled.
Driven by feedback
The fundamentals of the new experience haven’t changed. Our main goals are still based around the Fluent design language and focus on three pillars: cohesiveness, accessibility, and productivity. However, since we revealed the images in our first post, we got a lot of feedback about the things that our developers found important. In this version of the UI Refresh, you’ll get to experience a balance of the feedback we received with the accessibility requirements around things like clickable target space and reduction of visual clutter. This means a more inclusive experience to help everyone be more productive and comfortable while still maximizing code space and respecting the feedback you’ve shared with us. As an example of this, the first screenshots we shared, showed a reduction of nearly a full line of code in the editor space, but the editor in 17.9 preview 1 is only reduced by a quarter of a line.
We’ve found that we can meet the ideals of the Fluent design language while still prioritizing the things that our developers say are the most important. Now, this experience is ready for you to try so we can continue to build on your feedback. Our journey isn’t done yet; your feedback is absolutely critical! At this time, we don’t have a timeline for when this will be the primary UX for Visual Studio, which is why we’re spending so much time working with our users to get as much information as we possibly can.
A cohesive and colorful experience
One of the pillars of the Fluent UI design language is around cohesiveness. For the Visual Studio UI Refresh, this has been most evident in the simplification of the colors that we use in Visual Studio. Styles across Visual Studio before the UI Refresh used over 4,000 color tokens which were difficult to maintain and were easily misused. This frequently led to inconsistent experiences, accessibility issues and many other issues that led to an experience that didn’t feel cohesive. The new refreshed styles use only about one hundred tokens, which may still seem like a lot, but are much easier to maintain and will make it easier to spot incorrect use. This is leading to more consistency, and we believe will result in the cohesive experience that will make Visual Studio more comfortable to use.
Our current blue theme has some compatibility issues that we couldn’t iron out in time for Ignite, and instead of delaying this preview, we’ve had to make the decision to make it unavailable for now. We’re also aware that 3rd party themes may run into similar complications, so those may not work as expected with the UI Refresh yet. We’re working on both issues, so stay tuned and we’ll update as we make progress.
One of the benefits of streamlining the color service is that we can provide a fresher set of color themes beyond the basic “Dark” and “Light”. We’re calling these the new “Tinted” themes, and you can take a look at these below.
These tinted themes are inspired by Microsoft Edge and give Visual Studio a new, fresh look beyond the simple Light and Dark that have been the mainstay for the last decade. These themes can be found when the UI Refresh has been enabled and can be accessed either from the Tools > Theme or from the “color theme” combobox under Environment > Visual Experience in Tools\Options.
We want to hear from you
We’re excited to hear what folks think now that you can try out the UI Refresh instead of simply seeing static screenshots. We know that there’s still more we need to do. When switching to the tinted themes, customers not using the default Cascadia font will need to set their font back to their font of choice, and custom themes may not be compatible with the UI Refresh at this time. This is the first preview, but it certainly won’t be the last.
To share your feedback on the UI Refresh, you can join the discussion on Developer Community. If you want to share your feedback on the Tinted Themes, we’ve got a Developer Community discussion specifically for that too. We want to thank all our folks again for all the feedback that has gotten us this far and we’re eager to continue this conversation. Stay tuned here and in Developer Community as we continue down this journey.
While you’re fixing issues with the Blue theme, please fix the bug introduced somewhere around 17.5 or later that causes the Extra Contrast version of Blue theme to not show unused “using” statements (top of code file) and unused method parameters in a different color like they should be.
https://developercommunity.visualstudio.com/t/blue-extra-contrast-theme-doesnt-visu/10334392
I like the traditional blue theme, and I use the extra contrast version because it’s very similar, but with true black color for menus and text...
Just enabled this after reading a tweet/skeet about it. Don't remember which.
I love it. Once enabled, it switched to the Cool Breeze, and man is it literally a sight for sore eyes.
Added padding here and there helps a lot, and the gentle syntax coloring I find soothing. I have early onset mild diabetic glaucoma, and am short-sighted with an astigmatism in my left eye, so I have issues with headaches and blurry eyes. This change...
#2024dotNetFramework #fiscality #businessIntelligence #quantumSDK_updates #updates #supervised_machine_learning
I like it!
The changes are subtle but give useful visual clues.
Good job!
I don’t think it impedes the coding environment at all. I am surprised with the negative trolling. In particular from people who claim they don’t even use VS, that’s funny.
The fluent design language is clean and well thought of.
It brings out a nice cohesive user experience without dictating too much.
Looks great 💙
I hope VSCode themes will be compatible, at least with the converter
When we want to add a new item
There are several options
For example, adding a class, adding an interface, etc
But there is an option to add enum and struct
We hope that you add this feature and that there is a special icon for each of them
I’ve seen this feature before in Rider
The video showing the various color schemes really helps to see the various changes and I would say I have a good feeling at first. I like a lot the way the current document is more highlighted to the other tabs. I am not completely convinced on the separation between the various sub blocks: document well, solution explorer, output bottom. It may be a question of contrast between the background and the actual dialogs.
I...
I'm certain that I'm alone in this. But for the moment I think my preference is to simply stay with the current GUI of whichever Visual Studio version I'm using. But what *I* would really like to see for setting the Visual Studio environment is a 1-button action that will set my default font preferences across the entire UI, instead of having to go through line after line after line of drop down...
I would be interessted in a comparison of the UI-refresh with the old one with the opened document tabs not on the top but on the left side.
I guess there are no plans for an “UI Density control” as in Thunderbird?
I wish they spent that time on adding XAML designers for MAUI and WinUI.
As long as there is no designer, I will not touch either of them.
And the Code Review is broken for a very long time (I think it is broken since introduction)
Please fix what is broken before adding new stuff or tinkering with themes, colours and line spacing.
I agree, a XAML visual designer is direly needed. I don’t understand the huge step back. It impedes greately the adoption of MAUI and WinUI development.