I'm surprised to see that 29.1% of everyone is already using 2017 and 55.5% will be soon. For me, I like it when the community in general is using newer versions because I feel more comfortable using the latest C# version features.
Option (1569 votes so far) % total %
running VS 2017 since pre-release 7.39 7.39
I'm already using VS 2017 21.73 29.12
I will be moving to VS2017 ASAP 10.26 39.38
I'll upgrade soonish 16.12 55.5
I'll upgrade eventually 29.45 84.95
I can't see that I'll be upgrading 8.16 93.11
I don't use Visual Studio 6.88 99.99
I would bet a lot of CP members, like me, have installed VS2017 in order to test it, play with new C# language features, etc. ... but, are sticking with VS 2015, or earlier, for development.
«When I consider my brief span of life, swallowed up in an eternity before and after, the little space I fill, and even can see, engulfed in the infinite immensity of spaces of which I am ignorant, and which know me not, I am frightened, and am astonished at being here rather than there; for there is no reason why here rather than there, now rather than then.» Blaise Pascal
Well, I tried to install 2017. No ISO option. Undocumented offline download failed to work as "documented". Used web installer, after installation, app crashes within moments of opening. tried reboots, display driver updates, etc. I just finished uninstalling it, and will install 2015 sometime today.
Bringing out a new version of VS every two years may be good for your profitability but it is killing your customers, all of the programmers and developers that use it.
We don't need More frequent Releases of VS versions, we need better (more bug free, stable and reduced learning curve) versions.
I am near the end of my career so I plan of sticking with VS2015. (with all of its' flaws and yes it has plenty..) Give me the poison I just learned...
On the same general subject, fragmentation is the major problem with our industry. I know the Old Testament is not popular with the millennials and hipsters in our ranks but think "Tower of Babel" before designing a "New" Language, Tool, etc.
"Tower of Babel" triggered me. Sure, there are plenty of programming languages. Maybe to much. I'm also seeing the end of my career coming nearer and nearer, but that does not mean that I'm not willing to learn a new programming language, as long as it is handy and readable.
I wasn't implying that I am unwilling to learn a new language or use a new tool. Nor that any other programmer/developer be willing. It is our profession and we need to do what we have to, in order to get the job done.
I myself am learning / teaching myself C# as I am re-writing my software package that started life as a GW-BASIC, Flat file database (that I developed), in 1979. Over the years, the code went to Visual Basic from the first version to VB6, and the database to Microsoft ACCESS, and Microsoft SQL Server.
I am doing this so that my remaining clients all of whom have been with me more than 10 years will be able to find someone to support the code after I am gone. More C# programmers that VB programmers these days.
The point I was trying to make is that every engineer THINKS he can build a better mousetrap but only 1 in a million or so, actually can. I have no issues with creation of a new Language think Quantum Computing, where there is a demonstrated need for that language.
Most of the fools out there creating new languages are doing it for reasons of ego, when there is no real need for the language they created. Just because you "can" does not mean that you "Should". To put it another way, Different is not usually "better", it's just different.
I have been developing with VS 2015 since it's unveiling. When I engaged it I was just coming back into coding after being pulled away to manage for a while with a prior employer. I enjoy coding and was really stressing with the total lack of code before. Some mix would have been doable but it took a job change to get me back in the saddle.
That said, change for change sake isn't always a positive thing. Change for cause. The job was one for cause. I jumped on VS 2015 because it was just hitting the street and I didn't want to ramp up on something aging out sooner rather than later.
I've been watching VS 2017 real close and I think based on looking at what is going on in the 2015 platform and the potentials I see this is a change for cause that I cam embrace without hesitation.
I have initiated my request to update my work environment and am just waiting for permission to make the move in the office.
Last night I uninstalled the last of my dev environment from my home system and will load up 2017 when I get home tonight. For me it is time to turn the page and this gives me a leg up for when I'm allowed to swap out 17 for 15 at the office.
My shop is a mixture of vendor (large programs) and in-house programs (mostly small programs, some large), and we've recently dealt with ancient vendor code most recently compiled in an out-of-support IDE. It wouldn't compile in a new-ish IDE, requiring significant effort on the part of the vendor to update it. This is critical software so having it not updateable is not acceptable. [No, I don't believe the standards under which this software was originally written would be acceptable to most.]
Our unofficial policy is wait until the new IDE has a stable service pack and receives good reviews. New programs are then written in the new IDE and the oldest programs are recompiled in it. It's not painless but it solves more problems than it produces. Backwards compatibility is limited (try compiling VS 2005 programs in VS 2013 or VS 2015) and we find it better to do upgrades on our schedule instead of when forced by other conditions.
Realistically we'll be supporting the current IDE (once it is stable in our opinion) plus 2 or 3 revs back, with the third rev being phased out.
... but for now my understanding is that it won't (needs 8.1) so won't be changing my op.system just to get the latest VS. Yes, I'm really on 8(.0). It's stable and does what I need (apart from running VS2017 ) so why would I risk a change?
Fear? Not much, no. But if it ain't broke - and it isn't - why "fix" it? At an absolute minimum, I would have the learning curve to contend with. Then I've got to do all that research to find out how to STOP Win10 telling MS everything I'm doing. (Not paranoid, but even on a fast broadband I don't want everything clogging up when it's of zero value to me, and sometimes I'm on a metered connection). At worst - and there are plenty who've experienced this, even if it is a small percentage - my pc becomes unuseable, (due to non-startable, or hardware incompatabilities, or driver issues, or needing to upgrade other components I rely on). Plus there's the financial cost of an upgrade license.
At some point I'll presumably need to replace my 4-year old machine, and then I'll almost certainly take the grief of learning Windows all over again. (And certainly the grief of re-installing all the tools I use, and at that point "upgrading" to VS2017 (so long as it can still run all my legacy solutions unchanged). Until then, no thanks.
Last Visit: 31-Dec-99 19:00 Last Update: 16-Jan-22 0:11