Is there VB support?

[rrvenki]

Summary

Without long term VB support we are not jumping to this technology. Please say full VB support is going to be there or not.

API Changes

If Rosalyn compiler is going to be used there must be VB support. If its hardcoded with C# support only lets stop here only.

No matter Gold and Platinum in C#, unless there is VB full support this time we are not going to onboard this tech.

Intended Use Case

Convert/Migrate our existing 25+ years of investments in VB technology to be migrated to .NET 6. If not, we shall continue migrating the other VB implementations in non Microsoft platforms.

[saint4eva]

No.

[ayesc9000]

Definitely not. VB is old and outdated, and C# should be used if possible instead. In fact, you probably will not really gain any advantage by using VB on .NET 5/6. I would recommend looking into moving away from VB instead.

[Transis-Felipe]

@rrvenki Sad News but we must face the truth
Im also a vb dev Who trust when MS said that VB is first class.

[ayesc9000]

@rrvenki Sad News but we must face the truth
Im also a vb dev Who trust when MS said that VB is first class.

That was when Visual Basic launched in 1991. You should have seen this coming and moved away from Visual Basic when it was declared obsolete in 2008. Microsoft publicly stated that they did not intend to add any new features or support to Visual Basic for the rest of it's lifetime.

[GeraudFabien]

VB is old and outdated

Microsoft publicly stated that they did not intend to add any new features or support to Visual Basic for the rest of it's lifetime.

Since last year it will no get new feature. You make it sound like it was 10 years ago but it's one year ago since it's mars 2020. https://devblogs.microsoft.com/vbteam/visual-basic-support-planned-for-net-5-0/

No language feature doesn't mean no support. But seeing the amount of bug, lack of feature and performance of Xamarin i believe there is much more important thinks than VB.

PS: VB is still maintained

[ayesc9000]

Since last year it will no get new feature. You make it sound like it was 10 years ago but it's one year ago since it's mars 2020.

I should have worded my original comment better. I forgot that VB6 was declared obsolete in 2008 but the .NET version would continue on until after I posted my comment.

No language feature doesn't mean no support.

This is along the lines of what I meant to say.

[blenderfreaky]

Theres a visual studio extension for converting VB code to C# code.
I don't see why you wouldn't just move over to C#, basically every feature from VB exists in C# as well so conversion from VB to C# is essentially 1:1

[rrvenki]

VB and C type languages are two different worlds. C# fans recommending us to JUST MOVE TO C# is absolutely rude and unacceptable. Moving from near Human language to near Machine language is ridiculous. Its like moving everything to Passive voice from Active voice. Ex
Dim Age as Integer <- Active voice
int Age; <- Passive voice
Of course never to mention why there are so many curly braces and semicolons everywhere?
@Kiddo9000 mentioned VB is outdated. Why only because Microsoft liked other people's technology (C world) at the cost of their own technology (VB world).
After developing for 25+ years in various platforms its time to stick to VB. So for quite sometime we've moved to non microsoft vendors who provide latest VB which works in all platforms including IoT & Mobile.
As mentioned earlier, in the current form of VB we are working, we do not need .NET 6 or ms dev platform. Our apps are already working in windows and many other OSs with single code base written in non microsoft VB.

Our career flourished in VB which was given by MS. So we requested support from MS. If ignored why would we beg? We've no issues with non VB developers unlike the way you talk. We'd pity you one day you too would be in our position. Looks like VB creator itself is ousted from microsft eventhough he's the founder. Good Luck.

[drchilds]

Our career flourished in VB which was given by MS. So we requested support from MS. If ignored why would we beg? We've no issues with non VB developers unlike the way you talk. We'd pity you one day you too would be in our position. Looks like VB creator itself is ousted from microsft eventhough he's the founder. Good Luck.

Alan Cooper is not the founder of Microsoft.

All of .NET 6 is open source. If you want to add VB support, have at it.

[ayesc9000]

Moving from near Human language to near Machine language is ridiculous.

..What? C# is one of the easiest high-level languages you can learn right now. It is absolutely not "near machine".

Of course never to mention why there are so many curly braces and semicolons everywhere?

One of the most basic programming questions. The answer is so simple, you can find it a million times on Google.

@Kiddo9000 mentioned VB is outdated. Why only because Microsoft liked other people's technology (C world) at the cost of their own technology (VB world).

Visual Basic has run its life span. Microsoft has left it because of the little people still using it and the much better solutions out there. Believe it or not, creating and maintaining a programming language costs money. A lot of money. So why would Microsoft want to continue pouring money into a dying programming language?

This is why most devs branch out overtime to make sure they have the ability to easily move over to new technologies if their's becomes obsolete or something. You should never fix onto a single technology forever, because when that technology is gone, what are you going to do? Time, people, and technology move on whether you like it or not.

[guidevnet]

Let's be honest: if you know how to write VB.Net, the cost to migrate to C# is basically zero. I did this transition some years ago (even before VB was declared obsolete) and was completely painless. You just need to understand the syntax differences. The framework is the same.

It would be completely different, for example, if you want to migrate from VB.Net to Python: the framework and libs are different, therefore there is A LOT of learning involved. I can guarantee you that this is not true between VB and C#, the transition is completely seamless.

VB and C type languages are two different worlds. C# fans recommending us to JUST MOVE TO C# is absolutely rude and unacceptable. Moving from near Human language to near Machine language is ridiculous. Its like moving everything to Passive voice from Active voice. Ex
Dim Age as Integer <- Active voice
int Age; <- Passive voice
Of course never to mention why there are so many curly braces and semicolons everywhere?

I was in love with VB back then. But after a few months forcing myself to put "curly braces and semicolons everywhere", I realized that migrating to C# is very advantageous. You will get a more sophisticated, standard, mature, updated, predictable, less magical language. And you know: the lesser the magic, the more control you have. The only thing that I miss from the VB days is the "Handles" keyword, to wire an event handler on the function declaration. Other than that, I can say that I don't miss VB and I'm glad I did the transition.

[ayesc9000]

Let's be honest: if you know how to write VB.Net, the cost to migrate to C# is basically zero. I did this transition some years ago (even before VB was declared obsolete) and was completely painless. You just need to understand the syntax differences, because the framework is the same. It is completely different, for example, if you want to migrate from VB.Net to Python: the framework and libs are different, therefore there is A LOT of learning involved. I can guarantee you that this is not true between VB and C#, the transition is completely seamless.

VB and C type languages are two different worlds. C# fans recommending us to JUST MOVE TO C# is absolutely rude and unacceptable. Moving from near Human language to near Machine language is ridiculous. Its like moving everything to Passive voice from Active voice. Ex
Dim Age as Integer <- Active voice
int Age; <- Passive voice
Of course never to mention why there are so many curly braces and semicolons everywhere?

I was in love with VB back then. But after a few months forcing myself to put "curly braces and semicolons everywhere", I realized that migrating to C# is very advantageous. You will get a more sophisticated, standard, mature, updated, predictable, less magical language. And you know: the lesser the magic, the more control you have. The only thing that I miss from the VB days is the "Handles" keyword, to wire an event handler on the function declaration. Other than that, I can say that I don't miss VB and I'm glad I did the transition.

I too moved from VB to C# and the transition was a lot less painless than I thought it would be. I can back this up, moving to C# is very easy for any decently experienced developer.

[Redth]

There are no plans currently to support templates in .NET MAUI, however I'm not aware of any reason that you couldn't use VB to write a .NET MAUI application.

If someone wants to create and maintain some community templates that use VB for .NET MAUI we can see if it makes sense eventually to include them with the C# ones.

[DualBrain]

I love all of the C# centric people who are SUBJECT EXPERTS for a language they don't like, utilize, and/or care about. The misinformation in this thread is amazing; if anyone just takes a moment to review various repos / release notes... the story is very different than what is being suggested by these self-declared subject experts. In any case, I take a lot of positive hope that the statement:

I'm not aware of any reason that you couldn't use VB to write a .NET MAUI application.

... and ...

If someone wants to create and maintain some community templates that use VB for .NET MAUI we can see if it makes sense eventually to include them with the C# ones.

I'll have to see if I can carve out some time to investigate this further.