Simple but enough powerful. Has potential for further enhancements and room for new features and options. Will impatiently wait new updates with new added capabilities. Thank you developer for his time and effort!
Awesome, quick install, restart VS and adds "Theme" to your toolbar. I wanted this for big visual clue of what solution I was looking at when I have a lot open, when one VS window is green and the other is brown, it's pretty obvious.
Just some feedback on some of the colors. I use the "tan" scheme as a base and found everything great other than two issues that I fixed locally. I suspect they may be issues in other base schemes.
1) Scroll bar handle when not selected has almost no contrast to the background of the scroll bar which makes it very hard to find the handle to move it. When selected it becomes darker and there is more contrast but this is the opposite of when you need contrast.
2) In various places VS uses boxes around "toggle" objects to indicate the're selected. For instance the "Match case" toggle on the find/replace pop up. These boxes, again at least in "Tan", have almost no contrast to the background color so it's very easy to make mistakes.
Awesome plugin! Is there a mapping/explanation of what each name represents? (ie What is SortText?). When trying to customize it seems you have to either know what everything maps to already, or you have to apply one change at a time and see if that was the item you were hoping for.
Here's the answer:
reg delete HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\UseDebugColorScheme /f
reg delete HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0\ThemeColorCache /f
These keys left hanging around will prevent the WF designer from looking correct. Removing these keys fixed it all up for me.
Any chance we could get a VS2011 version of this software :) when I try to install it (Changing in the install files so it install to vs2011) I get this http://www.gratisimage.dk/graphic/images/2011/December/05/3ABB_4EDD2B0B.jpg :) (No matter which theme I choose)
Hi Matthew, great feature for the VS2010.
I work at a company called ISaGRAF. We produce software for industrial applications. Our new platform, which is a compiler for embedded applications, is based on Visual Studio 2010 isolated Shell. We have brand labelled the msdev.exe to Acp.exe (for Automation Collaborative Platform). Now my question is:
is it possible to use your theme editor in the ACP?
btw, once installed, we have our own registry keys... this is why i'm assuming that the theme editor wont work out-of-box.
I'm glad you figured that out! Sorry I haven't been able to keep more up-to-date on the forums, it's been a busy few months.
Yes, the theme values are stored in the registry. The registry key that immediately affects rendering in Visual Studio (using devenv's registry root as an example) is HKCU\Software\Microsoft\VisualStudio\10.0\UseDebugColorScheme\VSColors. Other data from the extension is stored in HKCU\Software\Microsoft\VisualStudio\10.0\ThemeColorCache (the serialized set of custom themes, the ID for the current theme, etc.)
Caveat: this themeing system is not guaranteed to be future-proof (that is, there can be breaking changes in the future versions of the Visual Studio shell that affect how this works).
I've created a (freeware) app that lets you create VS themes quickly by letting you select lots of colours and, for example, randomize a particular channel. The zip also includes 3 themes. I've put it at http://www.filedude.com/download/7g4YH3FRpQb0c76202d2. Sorry if I'm breaking some rule by putting this link here. Not sure how to share my app.
Is it possible to change the background and foreground colors of tooltips? I've tried changing anything that says "background" or "tool" in it. I run a high contrast theme in Aero, so the text in my tooltip is white, but so is the background.
Most tooltips in Visual Studio use default system colors. As far as I know, tooltips wouldn't use any colors this extension can influence. When you say you run a high contrast theme in Aero, do you mean that you're using one of the Windows system high contrast themes (like "High Contrast Black" or "High Contrast #1"?
There were some themes and when I change them then the background of menu changes, but when I try to use the "Customize colors" I cannot change it, it is possible to change some another backgrounds, but not the menu.
I've created a (freeware) app that lets you create VS themes quickly by letting you select lots of colours and, for example, randomize a particular channel.
The zip also includes 3 themes. I've put it at http://www.filedude.com/download/7g4YH3FRpQb0c76202d2.
Sorry if I'm breaking some rule by putting this link here. Not sure how to share my app.
Hi Mat, been looking forever for something like that, installed it immediately, only to find out the extension menu doesn't show. Tried to find that 'allow-non-admin' option (advice by Ryan Molden, http://blogs.msdn.com/b/visualstudio/archive/2010/01/04/changing-visual-studio-s-color-palette.aspx) in Tools>Option and could not.
Tried to run VS as admin - still not good enough... Any ideas?
My config is win7 x64, VS10 over VS08 (side by side). Perhaps an interesting detail would be that due to space limitations, had to install VS10 on 'D' drive, while VS08 is on 'C' drive.
Does the extension show up at all in the Extension Manager (Tools\Extension Manager)? It should NOT say [Disabled] next to the name. Selecting it should show Disable and Uninstall buttons next to the extension. Alternatively, you can check to see if the extension is installed by verifying that the folder "%LocalAppData%\Microsoft\VisualStudio\10.0\Extensions\Microsoft\Visual Studio Color Theme Editor\1.3" exists and has several files in it (including ThemeManagerPackage.dll).
If it does show up in the extension manager and is enabled, but doesn't work, I'll follow up with you to find out some more things. Hopefully this is the issue though!
Hello again, somehow MSDN site cut me off in the middle of transmission and later did not allow me to login.. Anyways, let me try again the post.
The extension is both installed and enabled; files are where they are supposed to be, here is their listing:
And, since I really like (need, actually) that extension, tried uninstall VS10, cleanup C drive, re-install in C (boy, that was tedious, mildly put). Too bad, no effect, exactly same behavior.
I'm sorry to hear that (and sorry for the delay)! Can you try this?
1. Go to Tools\Customize
2. Change to the Commands tab
3. Choose "Add New Menu"
4. Select the "New Menu" that was just created from the "Menu bar:" dropdown
5. Choose "Add Command..."
6. In the command list, there should be a category called "Theme" and there should be two commands in it. "cmdidDynamicThemeList" is the list of themes, and "cmdidThemeCustom" is the "Customize" command.
If the "Theme" category doesn't show up at all, can you verify if "Theme Manager 1.0" shows up in Help\About Microsoft Visual Studio's list of installed products? Showing up in that list should at least indicate that the extension did load successfully.
The Theme bar does not show up for me as well.
-The extension is appears in the extension manager and is not disabled.
-%LocalAppData%\Microsoft\VisualStudio\10.0\Extensions\Microsoft\Visual Studio Color Theme Editor\1.3 exists and is populated with the same files as Asparuh.
-It does not appear in the help box.
-The themes category does not exist in the command list.
I am using Windows 7 x64 Enterprise with Visual Studios 2010 Professional.
Is this extension still supported?
I wonder if you might both be hitting a bug in Visual Studio itself. Normally, when an extension is installed, Visual Studio's menu cache is invalidated, and Visual Studio rebuilds the cache to include menu items added by the extension. If that step didn't happen for some reason, it could explain why you don't see the extension's menu.
Can you try running "devenv /setup" from a Visual Studio 2010 command prompt? This command runs setup-type activities (like rebuilding the command cache), and shouldn't take more than a minute to complete. It also should not affect any of your user settings.
Hopefully this helps--I'm running out of ideas for why this doesn't work only a small percentage of the time.