I still use 2010, because there hasn't been anythign I needed enough in teh last three years to make me switch (and the Dark Side view and SHOUTY MENU put me off). If they had fixed some of the bugs I fight with that have been there since VS2005, then I'd have upgraded like a shot, but...
It's possible I'll upgrade to 2015, once SP1 is released - I've met Microsoft's idea of a "release ready" product before!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
On the shouty menu front, I stumbled across this[^] today. Had to swap 11.0 for 12.0 but it did work. Not so shouty now are you Mr V Studio? Hah!
I then moved from the Dark Side to the Light Side (Tools, Options, Environment, General, Color Theme) - which was almost as off-putting. So I opted for the middle of the road "blue" option. It was about then I spotted the "Turn off upper case in the menu bar option" in the same tab
So overall I think you're right to stick with 2010 for now
It seems lot of you use older versions of VS, especially at work.
It there any reason for that? Or there is just no rush for updating?
It is because we write software targeted for multiple OS versions. If you write something using VS6 for example, your targets will run properly (as long as the support files are installed) from anything from Windows 2000 up to Windows 2020 (whatever).
If you develop using Visual Studio 2012 for example, your code will not work on user machines running Vista or earlier.
At work it's VS2010. As for my own private projects I stick with 2008 and probably will for the duration. I develop almost entirely for the desktop and a little bit of web. All the tools I've bought (my reporting system, etc.) all plug in to it and I'm, frankly, sick of upgrading things all the time. I like the GUI of 2008 best of all of 'em, it's fast and the programs I write run on every version of Windows from XP up. Why cough up any more money, particularly if I'm not overextending this technology now, eh?
Biggest speedbump for me is that while the beancounters have bought an MSDN subscription, getting them to buy new versions of Re#er is a royal PITA. The version I have supports up to vs2012; but with that being a v1.0 for the new UI there wasn't much (read any) interest in upgrading to it.
I've played with VS2015; but the preview releases aren't licensed for production, so anyone using one of them *should* also be using an older one.
I've also got a handful of legacy apps still on VS03. For one the newest version is in VS2010; but a 3rd party UI component not working with .net 2.0 (or later) means I need to keep 03 around to do regression testing. The other I'm in the process of trying to upgrade to 2010; current status is Works on My Machine on the production box it's failing. I suspect the problem has to due with that box having locked down security permissions and .net 2+ replacing a single knob that can be turned to trust everything with a finer grained permission system, but need to do more investigation to be sure.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
You answered your own question. Rarely have I found a company that keeps abreast (within 1 year, let's say) of the latest software tools. And let's not even talk about keeping developers updated with the latest hardware!
Mainly we still use Visual Studio 6 (C and VB), sometimes I use 2008 because it is far more comfortable but the troubles of bringing back the code and the solution under VS6 for my colleague is a good deterrent.
Luckily it is extremely fast to boot, while 2008 is sluggish at best (we have cheap old workstations).
And most: more modern compiler and linker leads to smaller and faster code
I know, I benchmarked VS6, 2008 and 2012 on several computational heavy routines and proved that.
Still, our interface is VB6, our codebase is VC++6 with DSW and DSP files which must be mantained and most of all, my senior colleague and supervisor resist to the "upgrade" to VS2008 as stubbornly as a donkey
I'd like to move to 2008, maybe with a decent PC for a change, but it will be rough. It's highly probable we'll change directly to 2012 for the next interface, which will be WPF, but right now we're drowning in emergencies and can't make any progress in the improvement of the software.
It's pretty solid and I did not find anything that does not work as smooth as in VS 2013 [at least for the things I am interested in]. For me that is fully sufficient + I can use Roslyn without much trouble.