"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
2012 for my main development
2010 for SSIS
2008 for the occasional printing, so that I can see code printed in colour. The 2010 and 2012 colour printing functions are awful with huge margins and no control of how it is printed
It would be nice to have all back in the one IDE again.
Yes - I have tried that as well, but then I have Word decide to use its own tab settings rather than those I want. Guess I should set up a template I could paste into. Probably save some time as well..
Hadn't thought of that, but like the idea and will be implementing shortly. It might get me partially out of VS hell where versions which are meant to play alongside each other and don't. Intellisense being the biggest pain when it disappears.
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.
I'm retired. There's a nap for that...
Last Visit: 31-Dec-99 18:00 Last Update: 30-Sep-23 20:50