A group blog from members of the VB team
Who’s the “typical VB.NET developer”? Is there one? There are millions of VB.NET developers in the world, and they each have their own unique story. We decided to talk to some of them to find out what kinds of applications they’re building, what technologies they’re using, and what their favorite features are. Watch the interviews and find out for yourself who today's VB.NET developers really are!
View the interviews
Are you a VB, too? Tell your story here or leave a comment below.
Awesome interviews! I'm finding fewer & fewer VB programmers these days!
can u help me how to use vb.net. a program that can make a simple system .. like record system.. adding a person and save it to the database..
tnx. i hope your kind and consideration.. i need your help... god bless
Thanks for doing this. I think this is coming about 6 or 7 years too late. Microsoft really failed the VB community during the .Net transition. It has become more and more obvious that MS wants C# to be their language of choice. A simple look at the code samples on MSDN, and sites like ASP.Net and Silverlight.net show where MS reallly is.
I am a proud VB developer. VB is every bit as 'professional' a language as any curly brace language. In fact, I routinely find that a lot of the C# code I look at really isn't that great and I end up optimizing it.
I hope this campaign gets things going, but I really think you need help from the top to get VB back to where it should be. Get Bill Gates to come out of retirement long enough to announce that he is a VB (he was the original MS VB!). Then get Ballmer behind this effort. Then you will have something.
I need the code to print the immediate page which contains text and graphics. I.E. To print out a bank statrement. I know how to print graphics and a text file. I want to be able to let the user print the current page. Thanks Reply to firstname.lastname@example.org
Agree with Ed - MSFT *totally* failed the VB community with the .NET transition. The first comment by Tony sums up the result pretty well. It's over, folks. Some saw that back in 2001. Others, it seems, are only now coming to that conclusion. And poor Jim, what can we say? The newsgroups are [over there]. Better hustle along before MSFT destroys NNTP as well.
VB Over? Don’t know about that. I do know that VB.Net opportunities are far outweighed by C# ones. But I also know that there are still a lot of organizations still developing enterprise level applications in VB. But VB is not a popular language among hordes of H1B and L1 workers who are swarming over the US IT industry. They much prefer the Java like syntax of C# (since many of them are converts from the Java-J2EE crowd).
Think it’s a joke? Here’s an example of what is going on, in a Large National School Bus operating company in Cincinnati (won’t mention any names) they had a large enterprise wide billing application they where rewriting from VB6 to VB.Net. The company was a long term VB6 shop and wanted to stay with VB. They were not getting the application done on time (very seasonal) and they contracted me to come in and look over their Architecture, Implementation and to suggest remedies. They where even expressing reservations about staying with VB.Net if it was so troublesome to develop. Their IT department heads all thought they had a VB.Net application. They had entrusted the implementation to onsite H1B developers. The only American there who was hands on was the project manager, and he was 2 weeks new because they had just fired the H1B project manager.
As it turned out, everything had been done in C#, not VB.Net as the company’s specifications declared. I actually had to display on the wall the differences between VB and C# to management to get it into their heads that they did not have a VB.Net application that the crew they had hired had taken it upon themselves to switch to C# without any upper level management approval. What a hoot! On another project I had some IT managers push for C# because it is a more object oriented and a truly compiled language unlike VB.Net. (I had real fun with them)
C# is on a roll that it is on because of the change in who comprises the IT work force in America. I have been a Basic programmer since the early 80s up until now. I love the VB.Net environment. But as Ed and Karl are observing, Microsoft has not done a very good job in supporting the VB Community. Anyone with any comprehension can see clearly that MSFT provides the C# community with unbounded resources while it starves the VB community with a dearth of laughable support. There still are a lot of VB developers out there but they are dropping like flies. As for the VB Team? C’mon what are you doing? Why didn’t we have unsigned integers in the first version of Vb.Net? C# had it. How could you cripple VB with single line Lambdas while letting the C# community write multiple line Lambdas? What was your thinking on these and other such short comings?
Yes, Ibrahim, having to rewrite your application in order to "upgrade" <cough> qualifies as "has not done a very good job in supporting the VB Community". My bet is that this behavior is not over. While I still have a large portion of my app in VB, all my new features are in Delphi as I calmly transition the entire app to Delphi. It is what VB could have been, should have been, and would have been had it been driven by developer demand instead of being on some other mission. Worse, they failed the mission to get these developers and apps to DotNet. My move out of VB has been relatively painless, and I've been constantly surprised at what I find in Delphi (it's a lot more VB like than anyone on either side of that fence wants to admit). With regard to the VB team, we really tried hard to get their attention, and failed spectacularly. Sad deal all around.
Nothing has changed in the last five years. Microsoft still doesn't give a rat's tale about anything but *their* bottom line and apparently never will. To entrust any intellectual assets to a vehicle to which they are the sole vendor is pure folly given the track record. As has been said, there are alternatives to MS languages and the wise developer doesn't walk the path where the rug might at any time be pulled from beneath their feet at the whim of "some team" at MS. Microsoft's message to VB developers: “Go forth and prosper but don't do it in VB.”
we use vb and vb.net in our school....hope this language last!! ^^
Wow. I am a bit taken aback by some of the posts in reply to this topic. From the comments here, you would think that VB was Foxpro.
I dont know what else Microsoft is supposed to be doing in addition to the language upgrades, detailed documentation, free videos, free IDE (VS Express), free code, Code Plex itself, etc. etc. etc. There in no pleasing some people, I guess, but to claim that VB as a language is dead is silly. I dont see any indication whatsoever that Microsoft intends to pull the plug on it.
Its a very powerful language with huge following which has a syntax that is easily accesible to beginner programmers (unlike C#, I would add).
Can one of you list an example where Microsoft has forsaken VB in favor of C#? I must have missed it. They owe us another powerpack, but I dont know what else I can demand except Amanda Silvers cell phone number and some swag : -)
Lighten up, people.
VB PROGRAMMERS ARE LIKE PARASITE TO THE CODING> ANY DUMB MORON CAN CODE IN VB
Sam: Not to start a flame war, but I would say the same about C# (and PHP).
Any dumb moron can program in VB.NET, C#, or PHP. Are they not tools that are used by totally n000bs? Are they also all used to create large, enterprise applications? Yes.
Does VB need an upgrade? I dunno. The only feature I would like is a multiline string input:
Dim str as String = "This is line 1
this is line 2
this is line 3"
without having to break my string and use underscores. Even better would be Perl style input like
Dim str as String = q(This is line 1 "and it has quote"
this is line '3')
which is great for HTML and JS. Or:
Dim str as String = <<"EOS"
This is line 1
This is line 2
this is line 3
And as for C#, and lambdas, bahhh. I'll take optional parameters over that crap any day. Not to mention AddHandler instead of += (why reuse a math operator to do a totally different operation?)
Long live VB!
It is bad of Microsoft to dump all of those VB developers that have championed Microsoft develpment tools in the past in favour of C#. Some gratitude !
"Can one of you list an example where Microsoft has forsaken VB in favor of C#? I must have missed it ?"
XNA and game programming
Hey guys, we are supposed to be a "Visual Studio family". So no hard feelings between developers of Visual Basic and C# or any member of the family.
Speaking personally, yes it was so much easier to embrace VB a hundred times more than C# (which I comprehended later). With VB, not only making traditional code (database connection, networking etc), but also a very sophisticated applications like home automation, machine vision systems and SCADA monitoring.
If VB made me do my job as a first class automation engineer, then I'm proud to be VB. C# is awesome, but sorry guys, none can compete with me when it comes to Mechanical Automation and Machine Vision.