|
90% VB6? Brrrrr....
Perhaps he should change lives, not jobs... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I actually shuddered reading that 
"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
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
We went on VS2013 for all winforms and ASP.NET projects but we must stay on VS2008 for all Windows CE and Windows Mobile projects
|
|
|
|
|
because we make builds of our libs for all of those VS versions.
but i do primary dev in 2008 and 2013.
|
|
|
|
|
It depends on the project. I do not update old project when need maintenance, but new project goes to new VS. 2015 is for all the test projects...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
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.
|
|
|
|
|
Graham Cottle wrote: The 2010 and 2012 colour printing functions are awful with huge margins and no control of how it is printed
For years now I've simply copied and pasted into Word, where I can properly preview the results before printing.
Has the added benefit of being able to force page breaks to occur in sensible places.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
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..
|
|
|
|
|
I, too, use a Word Template (have since 1996), with the font, margins, header, etc. I like.
It has an AutoNew macro that pops up the OpenFile dialog so I can select the file I want, then it handles the rest.
|
|
|
|
|
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.
|
|
|
|
|
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?
|
|
|
|
|
I think the problem is that Visual Studio is heavy and slows down computer. VS 2012 is lighter and the usage is more fluent.
|
|
|
|
|
Most improvements are for c#, not c++
|
|
|
|
|
True, but the standards conformance has got better with each release.
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
On the framework/language/compiler level true.
But aren't the general IDE & performance improvements worth updating?
Recently I have been working with VS2010 and it's really heavy and slow comparing to 2012/2013...
|
|
|
|
|
I am using 2008, which is very fast. More importantly it's the last version to support macros, which critical to my productivity
|
|
|
|
|
The problem has a name: "Visual Basic". 
The VS 6 was the last version which has the legacy Visual Basic ("NOT DOT VB")
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
|
2012 is the standard here but WPF ribbon control is broken in it so until I get round to switching it out and using the fluent ribbon I will continue in 2010 for some projects
|
|
|
|
|
In some of the places I've worked the problem is with the purse-keepers (aka Accountants) ... they just can't be convinced that there is benefit in paying out money for upgrading 
|
|
|
|
|
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
|
|
|
|
|
A lot of times it's an issue with taking the time to upgrade and do regression testing. Every upgrade takes time (and time is money), so finding the time to do it is tricky.
|
|
|
|
|
Same here, we have a couple of projects which have been built with VS 2008, 2010. Currently there is no incentive which would justify the effort required for the upgrades.
|
|
|
|
|
You couple that with the frequency of releases of new VS versions... well, there's really no incentive for a business to try to keep up with that.
|
|
|
|
|
Because each new version worsens the experience. Even 2010 is harder to use than 2008.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
