Skip to main content

C# or VB.Net

Hey guys ! Im not raging a war to whatever language you prefer , Im just interested on your choice . Join the survey below and be counted .

Ill be doing a post on the differences between these 2 languages as well as pros and cons on using them . So please leave a comment why you are choosing C# or VB.Net . Thanks a lot .

Comments

Chris Ongsuco said…
I guess I'm just comfortable writing code in C#, you know, like IHero or IParanoia. =P

Kill me. hehehe
Patrik Hägne said…
I'm in no way a VB-hater as so many others are, in fact I do more than fifty percent of my development in VB. The lack of lambda statements (only one line lambda expressions are supported) is a BIIIIIG drawback in the new version.
Jon Limjap said…
I seriously don't understand why there is a need to compare VB and C#. Other than the issue of unmanaged code and synctactic sugar there is no real difference between the two languages.
Leon said…
It's just a matter of preference. You can use VB or C#, whichever you're comfortable and makes you productive.

I started with VB.NET but I prefer C# now, one of the reasons is that you can easily read/write javascript & java codes.
ely girang said…
VB.NET programmers prefer VB.BET, C# programmers prefer C#. It's the programmer's preference. I feel comfortable with C# so I code in C#.
Marvin said…
@jon

though they use the same framework , i assume there are some technical reasons that makes one better that the other in few areas (i suppose) .

to all,

i was curious about this topic because of one incident when a friend of mine was asked why he prefers C# over VB.NET and after giving answers that are almost similar to some of your comments , the interviewer just bluntly responded - "i dont like your answer" .

so perhaps there are some reasons that these interviewer know but most of us dont know or hes just being so rude.
Anonymous said…
I want to quote what the speaker in the SoCal .NET Group meeting that I recently attended:

"Asking a group who are the VB developers is just like asking who are gays"

whatever that meant, no one bothered to ask the speaker...
ely girang said…
The problem some developers are facing during job interviews is programming language discrimation which is not good. C# and VB.NET both have strengths and weaknesses so I guess they both be given due respect. Anyway, they were developed by the same company :)

And I guess we developers understand each other whether we're C# or VB.NET :)
Marvin said…
@ely

your right , programming language should not be issue .

one question that might be asked though is "are you willing to shift to another language?" =)

Popular posts from this blog

Hiding Unwanted Python Folders and Files in Visual Studio Code

Visual Studio Code is a universal editor and pretty good at it. However, the explorer view maybe cluttered with the automatically generated folders and files confusing developers. Python is no different. Below are example files and folders generated by Python.

The __pycache__ folder and *.pyc files  are totally unnecessary to the developer. To hide these files from the explorer view, we need to edit the settings.json for VSCode. Add the folder and the files as shown below:
Copy and paste the lines below :

"**/*.pyc":{"when":"$(basename).py"},"**/__pycache__":true

Getting Started with Stateless : A Lightweight Workflow Library Alternative for .NET

A year ago, I was looking for a simple workflow manager for a project I was working. Its a medium sized application that involves tracking the state of assets in the system. Back in 2008, Microsoft (MS) introduced new technologies along with the release of Visual Studio 2008: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), and Windows Workflow Foundation(WF). Having worked in a company utilizing mostly MS products for development, my first option was to go with WF. After doing some time reading and studying the library, I paused and decided it was too complex for my requirement. Using WF would be an overkill and the fact that it has, a rather, steep learning curve, there has to be another option. My mind toyed with the idea of developing a simple workflow library myself. It would be a learning experience but it might end up consuming a lot of time.

Why reinvent the wheel? So I started querying the internet for a better solution. I stumbled upon Stateless

Get Started with MongoDB Stitch : The New Backend As Service Offering from MongoDB

Halfway of this year, the guys from MongoDB launch their new backend as service product called MongoDB Stitch. While the launch is just for the beta, the promise of the service is quite interesting. MongoDB has been around for long now and some development stacks have been based on its database product, the MongoDB-ExpressJS-Angular-NodeJS (MEAN) and the MongoDB-ExpressJS-React-NodeJS (MERN) stacks to name a few. These stacks, however, relies on backend technology such as ExpressJS and NodeJS. The idea of provisioning servers and developing the backend solution makes it daunting for small to medium scale applications. MongoDB Atlas, at least made life much easier by providing on cloud database solution, but there must be a simpler solution, right? A solution the would stitch the backend and frontend together ( see what I did there ?).
MongoDB Stitch lets developers focus on building applications rather than on managing data manipulation code, service integration, or backend infrastruct…