Why is VB being forsaken?
-
All the programming I have done has been with VB then VB.NET. Microsoft keeps continues to develop and release it along side C# and the rest. However, over the last few years, I have seen very little new information out there regarding VB. Very few articles on Code Project and other sites. Oh, and I'm a subscriber to MSDN magazine and I haven't seen a single line of VB.NET code in .. in .. I can't even remember the last issue. I can say at least the last four issues there hasn't been anything in VB.NET. It's all been C#, C++ and even F# but no VB! Is Microsoft trying to push it to the side so it whithers and dies and hope that no one notices or pays attention? Even here on Code Project I've noted next to nothing new on VB. Every week I get the newsletter with all the new articles and rarely do I see anything on VB.NET. There may be one article among the 30 C# articles but that's on a good week. So, what am I supposed to do? Just stop using it, pick up a "Learning C# For Lonely, Left Behind VB.NET Programmers" and just think of VB.NET as fond memories of long ago? I have a hard time with such a concept. VB.NET has evolved into a good language and is capable of doing pretty much anything C# can do (using the .net framework, of course) so why isn't it promoted more by MS and others?
Maybe the C# guys have too much free personal time to make the articals and code examples. after a work day, I have a family and hobbies that in no way include computers; not that i haven't thought about writing up an article a time or two for VB. Stick with VB.net, it's a nice language. I've tried C#, I just feels like another knockoff of C, or Java adapted for modern times. Why MS doesn't promote VB more, I don't know, maybe thay just figure VB'ers will stick around. C# gets lots of add time to try and entice Java, C++ and others over to .NET. VB doesn't realy have any 'half cousins' sharing the same synthax to pull from.
-
All the programming I have done has been with VB then VB.NET. Microsoft keeps continues to develop and release it along side C# and the rest. However, over the last few years, I have seen very little new information out there regarding VB. Very few articles on Code Project and other sites. Oh, and I'm a subscriber to MSDN magazine and I haven't seen a single line of VB.NET code in .. in .. I can't even remember the last issue. I can say at least the last four issues there hasn't been anything in VB.NET. It's all been C#, C++ and even F# but no VB! Is Microsoft trying to push it to the side so it whithers and dies and hope that no one notices or pays attention? Even here on Code Project I've noted next to nothing new on VB. Every week I get the newsletter with all the new articles and rarely do I see anything on VB.NET. There may be one article among the 30 C# articles but that's on a good week. So, what am I supposed to do? Just stop using it, pick up a "Learning C# For Lonely, Left Behind VB.NET Programmers" and just think of VB.NET as fond memories of long ago? I have a hard time with such a concept. VB.NET has evolved into a good language and is capable of doing pretty much anything C# can do (using the .net framework, of course) so why isn't it promoted more by MS and others?
With a little work and surfing you can convert 99% of the C# articles to VB.NET. You might not be able to copy paste a whole program like with C# but divide it up, run it through a converter or figure out what each slice is doing and piece it back together. Even if most of your code is VB.NET, you can educate yourself by converting C# to VB.NET. You won't *KNOW* C# but you will be able to look and teach yourself to figure out what it going on in either lanugage. C# and VB.NET are so close now that soon I expect...and hope we will be able to click a checkbox or something to convert back and forth in the IDE. I'd also like to see the IDE allow C# and VB code live together. Why not? You can de-compile a VB or C# program from its machine code and get the correct language right? I know it's not *THAT* simple, but personally i'd like to stick with VB but toss in C# when I need it. We *should* be able to write this in the same class and have it work....Microsoft...hint..hint
Private Sub GetNumber()
Dim number As Integer
number = ReturnNumber(2, 2)
MessageBox.Show(CStr(number))
End Subprivate int ReturnNumber(int n1, int n2)
{
return n1 + n2;
}A Cup empty of myself.
-
All the programming I have done has been with VB then VB.NET. Microsoft keeps continues to develop and release it along side C# and the rest. However, over the last few years, I have seen very little new information out there regarding VB. Very few articles on Code Project and other sites. Oh, and I'm a subscriber to MSDN magazine and I haven't seen a single line of VB.NET code in .. in .. I can't even remember the last issue. I can say at least the last four issues there hasn't been anything in VB.NET. It's all been C#, C++ and even F# but no VB! Is Microsoft trying to push it to the side so it whithers and dies and hope that no one notices or pays attention? Even here on Code Project I've noted next to nothing new on VB. Every week I get the newsletter with all the new articles and rarely do I see anything on VB.NET. There may be one article among the 30 C# articles but that's on a good week. So, what am I supposed to do? Just stop using it, pick up a "Learning C# For Lonely, Left Behind VB.NET Programmers" and just think of VB.NET as fond memories of long ago? I have a hard time with such a concept. VB.NET has evolved into a good language and is capable of doing pretty much anything C# can do (using the .net framework, of course) so why isn't it promoted more by MS and others?
There are still plenty of VB articles in Visual Studio Magazine. Try it.