Upgraded from 1.42 to 1.43 and now my background is dark but settings still show defaults


Upgraded from 1.42 to 1.43 and now my background is dark but settings still show default light colors
VS2010 SP1
Something broke...

file attachments


blueonion wrote Apr 11, 2012 at 4:30 PM

Try resetting your colors. I had to go from color indexes to color refs. There's probably a mismatch somewhere. If that doesn't work then export and send me your color scheme. Also, make sure to read the release notes.

shoek wrote Apr 11, 2012 at 5:08 PM

I went to Fonts & Colors and clicked the "Use Defaults" button on the Text Editor category but no change after restarting VS2010. I exported just the Fonts & Colors section before I did this and that file is attached.

blueonion wrote Apr 11, 2012 at 6:00 PM

Downloaded and installed your colors. The extension is working as described in the release notes on the downloads page. This is a change from previous versions but is necessary to support dark background colors for the output window. The bottom line is that the extension uses background color of the text editor unless a specific background color is set for the VSColors. It's necessary to deal with some oddities in the VS color handling. You can change the output window background to dark in the fonts and settings dialog. If you want to stick with the white background for the output window, then you'll have to set the VSColors background colors explicitly to white.

shoek wrote Apr 11, 2012 at 7:55 PM

Hi... perhaps I am not understanding the release notes. I have not touched the colors settings because the "default" value is what I want (white background to text editor and output window, and VSColorOutput)
See sshot-2.png
But, I see black background on the text in the output window.
See sshot-3.png

Do I need to override the "default" White background color to be "White"
For the Text Editor | VSColorOutput Build Text category?

blueonion wrote Apr 11, 2012 at 10:04 PM

Sorry, got you confused with someone who sent me dark background scheme. I loaded up your color settings and all is well. Can't say what the issue is. Try changing your background color to black in the text editor, save and then change it back. Also, try uninstalling all extensions and then add VSColorOutput back in.

blueonion wrote Apr 13, 2012 at 1:27 PM

The change from 1.4.3 to 1.4.4 is that "auto colors" are no longer supported. This was necessary to support dark background colors. It's a confusing mess because I can't add the VSColors to the OuputWindow category which is why they appear in the Text Editor category (a limitation imposed by VS). Try changing your text editor background color to something non-standard like 250,250,250. This should change output window background color (may require a VS restart). Now change it back to the original color. The new colors should now be mapped to the output window as well (again, may require a VS restart).

xuefer wrote May 17, 2012 at 7:09 AM

i can reproduce this issue by checking plugin for visualstudio when i install vmware 8. and not reproduce if it re-run vmware 8 setup -> modify -> uncheck it

xuefer wrote May 22, 2012 at 8:17 AM

i can reproduce this issue after installed Subversion - ankhSVN. when devenv is open, output window "show output from" drop down list is default to ankhSVN(or vmware in previous report), maybe this is the problem. when build, it switch to "build", and maybe background color is not initialized there?

Zodman wrote Mar 5, 2013 at 2:19 AM

I think more recent versions resolve the problem.

Looks like the latest version isn't available through VS Extension Manager (at the time of writing, 1.4.5 was available from CodePlex but only 1.4.3 was available via VS Extension Manager). Download the VSIX from CodePlex and install that version.

HiredMind wrote Nov 4, 2013 at 10:09 PM

By the way if anyone is seeing this, as I just did with 1.4.6: I've found that 90% of the time it's VS2012 mangling the .suo file for your solution.

Every week or two I'll fire up VS and my previously loaded edit windows will be gone and the build output colors will be all screwed up, along with a bunch of other little things. But the solution is easy, just quit VS, delete your <solutionName>.suo file, and re-open your solution.