Programming Visual Basic Versus Visual C Sharp

Reasons for using Visual C #

There are some good reasons, Visual C #, VB before using it:

* If you already know Java or C + +, you will find C # to learn faster than learning VB

* There is less typing involved (VB commands are generally shorter)

* There are some more examples on the Internet to do with Visual Basic, as there are to do with C #

On the other hand, there are several reasons why you should use Visual Basic, listed below.

Reasons for using Visual Basic

This is not an exhaustive list (which you can link the blog to see below for a more detailed discussion), but it's a good start.

Mainly Visual Basic commands are easier to read. Consider these two commands:

First IF txtProduct.Text = "" = False Then txtProduct.Visible

Second if (txtProduct.Text = "") {} = false txtProduct.Visible

what seems more readable to you? I plump for the first time each. VB is more striking, but on condition that the IntelliSense in Visual Studio does make it more bearable, and the resulting code is much easier to read.

Another thing I dislike about C # is the requirement to place a semicolon at the end of each command. It's just not a natural thing to do.

Worst of all is the insistence in C #, a variable that is not the same as a variable. Everything is case sensitive, which makes it much more likely that you will make mistakes. There is really no good reason for this other than the legacy of existing programming.

In addition to all these things, there are many small defect: the commutator operator is not so easy to use than the equivalent VB Select Case, you can not just resize tables and optional arguments have been introduced with Visual C # 2010th

Completion

So my conclusion would be if a free hand (and it may well be good reasons why it is not), you use Visual Basic. If on the other hand, you have a team of C-or Java-legacy programmers who have to use a language with variables are case sensitive, then let them use Visual C #.

Finally, all built into the chassis the.NET on something called CLR or Common Language Runtime, so it is not too much, the language you use is important. Just do not blame me if you keep the spelling of variables in the different cases, or semicolons missing from the end of the order. And let the braces!

If you have these comments (perhaps you're die-hard C programmers) do not agree, comment and tell me what I missed!

You can learn more about why Visual Basic is better than C # to read. Alternatively, if you just want training in Visual Basic or C # have a look at the Wise Owl site.