Right at the top there you can see both Visual Basic and C# designated as their 2017 versions. I suppose Microsoft could just renumber the same old program with every release of Visual Studio, but I doubt they'd do even that much if they wanted to put a language out to pasture. It is also interesting to compare the [url=https://www.tiobe.com/tiobe-index/csharp/]historical ranking for C#[/url] with the [url=https://www.tiobe.com/tiobe-index/visual-basic-dotnet/]historical ranking of Visual Basic[/url]. C# ranks a bit higher, but has trended downward since its peak in 2012, while Visual Basic has trended upwards over the same span of years. (Not that the Tiobe index is conclusive, but it is interesting.) I think Les's characterization is quite apt. Back in the '80s, a computer researcher I knew predicted that, "eventually, all languages will converge to something like C." Being a long-time C fan, I tried C# first, when I was recently motivated to look for an all-Microsoft way to get something done. (Mostly, I write in Java and use the JNI when I need something specific to Windows that Java can't do on its own. This time, I needed to avoid relying on there being, or having to install, a Java Runtime Environment on my users' machines.) I was kind of surprised by how much if, at least upon my first glance, did [i]not[/i] look like C. In particular, I saw some stuff in square brackets that kind of put me off. Having learned Visual Basic long ago, I looked at that again. Imagine my surprise to discover that, since my last go-round with it (when it was still called Visual Basic 6), it had become a truly object oriented language. While it is true that Visual Basic does not use curly brackets, nor end a statement with a semicolon, I'm pretty much finding that its current form makes writing the Visual Basic equivalent of a Java method mostly a matter of looking up the comparable keyword. (I posted a handy cheat-sheet that illustrates how much the two languages have grown alike, grammatically if not syntactically.) So, it appears that, for now, whether one uses C# or Visual Basic is a matter of personal preference, there being no capability unique to either. And, as far as I can tell, Microsoft remains equally committed to both for the foreseeable future (which, when we are talking about Microsoft, maybe only be about twenty minutes, but that's how it is for both languages.) Hope you'll post here often. New forums need new input!
Where did you see that, Claude?
Try Googling "Java is dead" and you'll see what I mean.