A great tool that simply works and adds color to the editor. Once again though, something that should be part of Visual Studio to begin instead of telling everyone to love staring at a gray-washed ide all day.
This is GREAT. Suggestion: can a theme be linked to a solution? Imagine each solution a developer works on would have its own color scheme ... Technically this would just require an extra property in the .sln file referring to that scheme.
Somewhere, at Microsoft, is a manager. This person probably has a crisp manner of speaking, excellent posture, and uses bombastic words like "deliverable" and "core competency" and "chime in". And that person is a friggin' idiot. To that idiot: I would like to tell you something that neither your mother, your father, your 1st-grade teacher, your first girlfriend (or boyfriend) (or Metro-friend), your high-school counselor, your college counselor, your grad-school counselor, your trust-fund trustee, your grand-parents, or your dog told you: You are a bona-fide idiot. You live in a world where you can be utterly incompetent, and still stay afloat, because other people around you have been pulling your weight from birth. If you had been born into an environment where latte was a type of weapon, I can assure you: VS2012 WOULD NOT LOOK SO HORRIFIC. NO, I AM NOT YELLING AT YOU. I AM MERELY FOLLOWING YOUR LEAD.
Matt, this is fantastic work! Such a pity MS didn't get you to do this at the beginning, instead of trying to force the new light/dark themes on everyone, whether they wanted the change or not. The light/dark themes would have been so much better received if they had been a choice, not rammed down our throats.
But the problem is, I only found the 2.1 version by accident (but a very pleasant one it was), then again, I only found the updated 2.2 version by accident as well. So much frustration could have been saved for a lot of people, if they knew only about your extension.
One odd thing though, VS didn't flag the new version as an available update, even though I had the original one installed already.
I love the sound of the things that you're "thinking about" doing. Can't wait to see what you come up with.
Hi. On my copy of VS2012 the colour of the document tabs seems to be fixed: aspx forms and code behind get a rather nasty brick red, .cs classes a sort of British Racing Green. The document with the focus doesn't really stand out, particularly for green tabs and it sometimes takes me a while to realise I'm not on the tab I thought I was. This doesn't seem to be under the control of the theme editor - is there any way to change it?
I'm using VS 2012 as a component of Sql Server Data Tools. As such this is the "integrated" version, not "Professional. As a result I apparently can't install this extension, which is a bummer, because I can't stand the look of VS 2012!!!!
Is there w reason why you can't support other versions?
The Color Theme Editor for VS 2010 let me set a color theme for each instance of VS while it was running. That is, after I started an instance of VS 2010 I could select a Theme. Then I could start a second instance of VS 2010 and set its Theme to a different color. This made it easy to identify which instance I was working with.
In VS 2012, if I have two instances running and change the color of one instance it also changes the color of the second instance.
Is there any way to include the logic from the 2010 version. It was very useful.
I installed the plugin while having my custom colors. I noticed that it changed some of the colors here and there and I tried to import them back from settings file. I realized that the studio has stopped importing colors and fonts. I uninstalled the plugin but this didn't fix the problem. So now I have a spoiled color theme and broken import settings feature. Also on every change of theme the font is reset to some strange font and I have to go change it manually from the options. All this is happening on VS 2012 Professional.
Can you suggest any fix other than uninstall and install of VS?
Hi I have setup my windows colours so that I don't feel like I'm staring at the sun all day with the glaring white paper that is Visual studios default.
However I cannot see (no pun intended) how to change VS2012 workspace background colours to my windows colour.
It would be good if there was an option to Pick-up the windows (theme) colour either entirely or per item.
Until I can change the paper colour I'll have to give VS2012 a miss or ask my lawyer about what come back on MS there would be for consequential damage from using the UI (joke).
Please help us that customise windows colours for Usability reasons!!!!
I can think of two options:
1. Use a High Contrast windows theme, and customize those colors. In this case, Visual Studio will use only Windows theme colors.
2. Customize Visual Studio colors using this extension to be what you want (perhaps starting from the Dark theme is closer to what you want).
The big problem with "using Windows colors" is that Windows exposes a very, very small set of colors, but Visual Studio is a complex application that requires more nuanced color choices. This extension currently gives you maximum control over that nuance.
What element in the Theme Editor determines the background color when working with SSIS packages? Specifically the Control Flow and Data Flow pages. I copied the Dark installed theme and wanted to tweak a few colors, but leave the background like it was in the installed theme. However it changes the background color to an off-white color after copying the installed theme.
I'm not familiar with SSIS packages, but based on the description of the problem, my guess is that its UI has handled theming incorrectly in some way (perhaps their "Dark" colors are tied specifically to that theme's ID rather than defining colors that can be redefined for any theme).
The standard "fonts and colors" dialog in VS has a preview box that shows a sample line of code in the selected colour. This is helpful for visualising the colour in context and is the only thing I miss from this extension.
Any chance of implementing that, either in this or the 2013 version? Thanks.
That would be a great feature--I will add that to my list. For the colors that come from Fonts & Colors, it should be straightforward to show the same type of preview. For colors that are outside the editor, there's not currently metadata about what type of text to draw on that color in all cases, so that may be trickier to implement.
I've just uploaded the 2013 version today (available here: http://visualstudiogallery.msdn.microsoft.com/9e08e5d3-6eb4-4e73-a045-6ea2a5cbdabe). You should be able to export custom themes from 2012 and import them in 2013. Feedback about the import experience is appreciated!
I downloaded and installed this as soon as I came in this morning. The import process was totally painless. In fact, it picked up my existing themes and even applied the one that I was using in 2012, exactly what I had wanted!! Thank you for your continued efforts to make my coding world a more colorful place!!
Earlier versions of this extension seemed to create extensions (& possibly VSIX files for them), but the only method for saving/sharing themes in the current version of this extension seems to be exporting/importing vstheme files.
The VSIX method was a far easier (& more reliable) way to be able to save a theme, then install it later (say after a machine rebuild). I don't seem to be able to find where the VSIX files were stored, but I can see that extensions have been installed in the Extension Manager in VS 2012.
Why was the VSIX method removed? And will it be restored (no pun intended) in a near future version of this extension (particularly for VS 2013)?
This extension doesn't let you do this. Visual Studio inherently supports only one theme per registry location. You can launch Visual Studio with an alternate registry location, and that Visual Studio instance would be able to have a different theme, but it would also have completely isolated settings for every other Visual Studio feature.
If you want to try it out, just run "devenv /rootsuffix MySpecialSettingsGroup".