There is nothing wrong in programming in VB.NET. It's a tool for developing apps with, and there's a lot of elitist claptrap surrounding people's opinions on it. One of the best developers I know wrote a lot of great apps with it. He ended up as a PM at Microsoft.
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
Thanks Pete, I think some people need to hear that coming from someone of your level of expertise. VB is my bread and butter language and they pay me a decent wage for for doing so. I'm also the GoTo guy for converting legacy VB 6 apps to C# or VB.NET.
I still have a spot in my heart for VB 6, but I haven't forgotten thr frusrations of debuggung applications with undeclared or loosely declared variables.
I worked as a developer back in the 80s (dBaseII, Lotus 123 macros, Wang Glossaries and MS Basic). But my toy at home was a TI-994a. I still have the old manual for TI Basic as a keepsake. When I left the depravity of office environments behind I didn't lose my love for coding, and I just sort of stuck with Basic. It's more intuitive (for me) than any other language I've ever tried.
If you want to try something truly bizarre, download Presentation Wizard[^] and try AM's A.N.I.M.A.L. programming language. It's not overly complicated but the syntax is backasswards from anything else I've ever tried.
Welcome to one of the nicest languages ever with some of the greatest flaws ever
VB.NET isn't so bad once you get used to it. I prefer it over C#.
Just enjoy not having to type (); manually at the end of each sentence...
Or break; after each case of a switch statement, while falling through isn't allowed anyway...
Or an opening and closing bracket after just about every other line of code...
Just make sure you put Option Strict On and don't talk to VB programmers that have been around since the 90's
Yeah, I've seen recent C# code that will put shame to bad 90's VB code
I've also seen quite some bad VB code.
Then again, I've seen bad English and bad Dutch...
It's the skill of the programmer that matters, not the language (although having Option Strict Off by default is inviting people to write bad code in VB ).
I'm as proficient in C# as I am in VB, though I prefer the latter to read and write (if done well)
Well, don't listen to all that crap. You can answer to those people that a language is nothing more than a tool to use to build stuff.
If they dislike VB, then that's their propblem, not yours. If the job requires to use an old, gnarly and obscure tool (not that's what I think of VB, I used to develop everyday using VB6 and VBScript, and contributed to great apps developped with it and I still nurture a foundness for that good old time ) that they don't know, tell them it is no reason to make fun of you.
No on should be laughed at because they did their job as per spec, nobody chooses what they really want to do (not at a corporate level at least, if you are an indie, that an other story).
Walk with your head straight and keep your hight esteem of yourself.
If you are able to develop in many different languages and they don't, then you're definitely better than them.
At least VB made visual design easy, HTML+JS is still a long way off on that front.
So many people queue up to knock VB, but just look at the god-awful, copy-and-paste-designed JS lurking behind many a web page and you'll find yourself wishing for a return to simpler days.
The payroll rules engine I have is written in VB.Net. A few hundred thousand people from California to Puerto Rico get their paychecks as a result of that code. I don't think any of them care that it's written in VB.Net, do you?
No apologies necessary and you don't have to keep a "low" profile. Code away pal!
Ah, I always enjoy another VB vs. C# discussion. As Woody Allen in one of his movies remembered his dad bickering with his mom, "OK! Have it it your way! The Atlantic Ocean is better than the Pacific!" As a programmer who cut his teeth on Fortran in the sixties, I have a number of languages under my belt, including the various dialects of C. My favorite was Pascal - now there was a readable language. I admit to having become a lazy man in my dotage. In these modern times I gravitate to VB.NET. My.Computer sure is handy! Yes, I run into incredulity and condescension from the young professional IT types (whippersnappers!), but the fact is the results are the same with either language and are not improved by curly brackets, no matter how many.
Nothing wrong with that! I even do maintenance on VB6 programs and VBA stuff (mainly in Excel)! Why? It works and nobody wants to spend a single buck more then absolutely needed. Just funny the client asked for a particular language!? "We don't have any business requirements yet and actually we are not sure what we want at all but it has to be written in VB.NET". Reminds my of some business departments in our company
If your any good at C# within a day or two you'll be cranking out VB.NET code like it's nothing. It's not a bad language at all, though it's a little verbose in my opinion. At the end of the day your writing against the same .NET framework you already know.