VS 2010 color config - am I missing something?
-
Yes, it was a joke! I'm sorry if anyone has taken offense. :( I suppose I should have put it under the joke icon, I am surprised that some took it seriously. For the record, I seriously doubt that Microsoft would actually change how to access features just to charge people money to learn how to access them. (Microsoft VS is one of the tools I use to make my living. And yes they do get plenty of money from the MSDN subscriptions and licenses from my company)
It was broke, so I fixed it.
My apologies. I need to recalibrate my sarcasm detector. :-O
/* Charles Oppermann */ http://weblogs.asp.net/chuckop
-
I've never been a big fan of the Walt Disney approach to text editor color schemes, so the first thing I typically do when setting up a new install is spin through the colors of the editor and switch them all to black on white. Okay, I set the comments to blue, but that's pretty much it. It's tedious enough as it is since I have to manually set each and every option, one at a time (note to MS VS devs: there's this new feature called multiple select, you might want to go to a conference and learn about it). However, in going through this exercise with VS 2010, it's even worse. In a number of options (selected text, for example), either the foreground or background selection controls are disabled, forcing me to live with the colors VS comes with. Uh, isn't the point of "options" the ability to change them? Am I missing something obvious here, or have they taken away my ability to completely control the colors used in the VS editor? If there's a switch to flip somewhere, I'd love to know about it. The only thing I can find to flip at the moment is... oops - there's my kid sister again. Dang!
Christopher Duncan Author of The Career Programmer Watch Bad Programmer! - Premieres May, 2011
After resisting them initially (initially spans years), I now believe they are very helpful. > The darker schemes are certainly friendly to the eyes. > Having a different color scheme does help impart the 'geek'y attribute to you especially when most of the developers around you live with the default scheme. Changing them individually is a pain. I started with a dark theme and modified few settings to my liking. This way, I din't have to change a whole lot. I still don't like the VS theme switching (maybe the default theme is what I find the best).
-
I've never been a big fan of the Walt Disney approach to text editor color schemes, so the first thing I typically do when setting up a new install is spin through the colors of the editor and switch them all to black on white. Okay, I set the comments to blue, but that's pretty much it. It's tedious enough as it is since I have to manually set each and every option, one at a time (note to MS VS devs: there's this new feature called multiple select, you might want to go to a conference and learn about it). However, in going through this exercise with VS 2010, it's even worse. In a number of options (selected text, for example), either the foreground or background selection controls are disabled, forcing me to live with the colors VS comes with. Uh, isn't the point of "options" the ability to change them? Am I missing something obvious here, or have they taken away my ability to completely control the colors used in the VS editor? If there's a switch to flip somewhere, I'd love to know about it. The only thing I can find to flip at the moment is... oops - there's my kid sister again. Dang!
Christopher Duncan Author of The Career Programmer Watch Bad Programmer! - Premieres May, 2011
I can't speak to the ability to change foregrounds/backgrounds on certain elements. I suspect it has to do with a particular element only changing the back/foreground, and relying on another element to provide the other one. But you can save yourself a lot of time by simply saving off your settings: Tools->Import and Export Settings At least you'll only have to do it once, and it saves all your keyboard customizations and many other things too.
Before .NET 4.0, object Universe = NULL;