Choose vb.net or C #

And what about vb.net?


In the view of many real developers, VB is like a toy language, from a certain point of view, it is true. So far, VB is far more than the two or three weaknesses we know. But VB.net is really as powerful as C #. NET development language. Some people say it's more powerful.

Vb. NET has built-in (insert feature) support;

"VB. NET built a lot of things like string manipulation (Mid, INSTR, etc.) and type conversions (e.g. CInt). C # lacks these built-in support, so what I need is hard to find in C #.

If you catch these you should mid or CInt function, and ultimately think that this is vb.net stronger than C # evidence, you'd better go to see Microsoft.VisualBasic namespace. You will find most vb.net internal commands and application functions there. Once these features have been saved in namespace, any CLS-compliant language can use them, as shown in listing a. These examples weaken our argument, don't they?

Better bundled support is not supported

"VB. NET and COM entity bundle support is better. "I just saw a little bit of it, and I decided not to have any reason to support it again." From what I have observed so far, this is not true. C # and vb.net must use runtime callable packaging and equivalent source code to execute an earlier entity. Similarly, executing a late entity requires the same amount of code.

Vb. NET uses background compilation in the IDE

If you can't find another example of a good development environment in VB, you have to at least admit that its source code editing is very characteristic. You can literally exclude errors from your code while typing. Trouble is, those are retarded. Compile error message boxes always bounce, and if you turn your horn too loud, the beep may scare you.

Visual Studio.NET avoids this scare until you have modified it and handled some negative errors, prompting the system to go through Microsoft's improvements: He would underline the error statements below.

Vb. NET background compiler/Syntax checker is very complex and very polite to point out your mistakes. In some ways, it can tell you more accurately how to modify your source code errors. When C # has its own grammar checker, and can detect parentheses matching, calculate the number of parentheses, show the missing semicolon, but it still can not be used as simple as vb.net. It would really annoy me to continue discussing the superiority of both languages, but Microsoft's words are indeed a truth, and that is all. NET languages are all created on an equal footing. Those who argue that C # is superior to vb.net (and vice versa) are just as wrong as those who are comparing wages.

I would like to stress that visionary technology companies are no longer looking for programmers with some kind of development language experience, but rather looking for those who have. NET class Library development experience programmer. So I advise you not to worry too much about what your choice is: Just find a language that you feel interested in learning, and carefully learn his frame structure.

If you end up thinking I'm wrong and the market doesn't require you to choose a language, just laugh at me.