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

renaming default namespaces for VSTO projects in VS2008

So here is the scenario , you are starting a VSTO project and decided that your default namespace is ExcelAddInTesterApp . You created the project and started coding the project. After several days , your boss called and said "hey marvin , make use of this namespace OurCompany.ExcelAddInTesterApp , we have to add our company name to it got it?" . You get back to your machine thinking its just a simple property just like any project you've been working on. So you right clicked the VSTO project and hit properties . Boom! What the F@#$? The default namespace textbox is disabled!!!!



I've been through this and I googled for ways to do it and ended up with a blog from a Microsoft MVP telling me it can't be done because it is disabled. Then I thought of Refactoring, the beauty and grandeur of the renaming process. I selected the namespace and hit the refactor menu hoping that this would solve the problem . Unfortunately , it did not rather it displayed the message box …

Automatic Properties and Object Initializers in .Net 3.5

With the release of .Net 3.5 alongside with Visual Studio 2008 , new enhancements was again introduced . Some maybe well pronounced such as the inclusion of WCF, WPF , LINQ in .Net 3.0 and some just came unnoticed. If you have been accustomed of using a particular method or technique in implementing a certain code in .Net 2.0 , because of backward compatibility , you may not even notice that there are new ways of implementing it in .Net 3.5.

Here are two new concepts in .Net 3.5 that a developer may not notice ( at least in my opinion ) : Automatic Properties and Object Initializers . To illustrate these two , I am going to present the pre-.Net 3.5 way (.Net 2.0) and the .Net 3.5 way in creating a simple class with simple properties.

Automatic Properties

Creating a class can be tedious , especially when working with a list of properties , . One way to get around having to type the code for a private field and its public property getter and setter is to use a refactoring tool. However, …