Is VB developed on the same scale as C#? [closed]

开发者_运维知识库 As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 12 years ago.

I know VB is still very popular, but does Microsoft put the same effort into developing VB as they do for C#? Will VB eventually fade away?

---

Microsoft is focusing on making C# and VB.NET (not VB6) similar in what is being termed as a "co-evolution" of the languages. We can see this with C# 4.0 adopting optional parameters and VB.NET 10 adding support for automatic properties and multi-statement lambdas.

This is supported by the following links:

• Q&A: Microsoft's Lisa Feigenbaum Talks About C#
• Luca Bolognese (PDC '09) - Future Directions for C# and Visual Basic
• Luca Bolognese: C# and VB.NET Co-Evolution - The Twain Shall Meet

---

Very few people are adding to VB.NET numbers but people already started with VB and then moved to VB.NET will stay around for a long time.

---

I started in this line of work developing Access apps. VBA 6 is still used in Access 2010, and my colleagues of old refer to .NET as "LINQ and other stuff". The point being, they don't need .NET "luxuries" to satisfy their clients needs cheaply and effectively.

VBA being a whole lot less than VB6. So the same will apply to many VB6 developers.

However, I think the question (although not clearly stated) refers to VB.NET. In that case, I think VB.NET gets as much attention as C#. The big difference is that most of the best samples are in C# and as development nowadays depends heavily on googling for samples, that tilts the balance in favour of C#. But only just. And there are things that are easier to do in VB.NET than they are in C#, although C# 4.0, with optional parameters, etc, is closing that gap.

Me, I left Access partly because I live in a rural area so it makes more sense to develop apps for the web that don't require me to travel to client's offices. But mainly, because aesthetics are important to me and I HATED the VB syntax.

Other people hate curly brackets. I think they illustrate the scope of what each item of code has access to, but there you go, horses for courses.

No. Categorically NO. VB.NET will not fade away, and VB6 and VBA have not yet exhausted their potential.