C#, VB and the .net framework

[CodedFire]

So ive been learning C# as part of my get a job plan, i felt if i knew the two main .net languages i could put a .net programmer on my CV as apposed to a VB programer.

Anyhow, one thing ive noticed is C# is taugth as a language your going to use in a "serious" envoiroment. For instance, a vb refrence book is alot bigger because it list all the common controls and their functionality and proceeds something like this: Intro, Variables, Code Control (looping etc), Controls, Methods and Functions, Classes, Databases, Xml, etc

C# on the other hand is alot more compact, it shows you the textbox and the button explains what they are and tells you that all controls are fundamentily the same use MSDN library for the workings of other controls.

Another comparission is how code is structered. For instance the example to make a calculator in vb is structured something like this. Desigin the form, write a method to handle calculations and tie it to the button handlers. In C# though the idea is to design a class that handles the calculations and this way it is independent of the interface. This means you can have the main ide reference the class and also a "test" ide in order to expose any potential bugs. Obviously for a claculator this is not the best design but i the concept really helps understand OO and keeping the interface and bussiness code seperate.

It just seems that VB is taught as a hobbiest language were as C# is taught more as an everyday language to be used proffessionally. I cant understand why!

Sorry i know this is a random rant but learning all about each language and the underlying framework is really quite fascinating! It also give great perspective on the two languages and the framework as a whole!

[RhinoBull]

Anyhow, one thing ive noticed is C# is taugth as a language your going to use in a "serious" envoiroment...

I work in what you call "serious envoiroment" and we are VB shop - All the development is done in VB 2005.
In .Net language is irrelevant because framework is like "one to many" relationship - each class/functionality is equally accessible by any language.
What's different [mainly] is the syntax. But on your resume you should be more specific about the language you know however.

[CodedFire]

Oh i understand that the differences between both languages is not much what i cant understand is why one (vb) is taught in refrences more laxy dazy than the other (c#)

[RhinoBull]

Maybe because VB is still been treated [by some "writers" ] as a language for novice programmers... Vast majority would disagree with this though.

[CodedFire]

So would i! i do think that it would be better if writters would treat it the same as C#. Ive ordered some books from Apress im hoping they are better than others as i like their books regarding C# and the framework in general!

[RhinoBull]

Well, just so you are aware that there is no perfect book - never was and never will be.
Each book however offers something unique despite they all look alike - uniqueness really depends on author's expertise.

Good luck!

[RobDog888]

If you are getting that kind of teachings from that book then I would suggest getting another book. check out the books reviews first.

See the response from the actual Microsoft VB developers:
http://vbforums.com/showthread.php?t=500243
http://vbforums.com/showthread.php?t=500263

[ComputerJy]

VB is as serious as C#, they both have the same functionality because deep down they rely on the .NET framework, so that makes them a bit even with all other .Net languages (including IronPython, F#, .... etc)

The reason writers treat VB as a novice programmer's language is beacuse it's one of the best entrances to the world of programming for people who know English.

And by the way, the structure of the code is all about the developer, it's never about the language, given that .Net developers depend on the IDE to do the basics (Drag & Drop controls are "Friend" in VB and "private" in C#) but you can always change that. Other than that, it's all you.

Another reason why VB books are usually for novice is because of the great work Microsoft marketing people are doing to make people capable of creating their own small applications. It's an attraction thing.

Besides, who can resist using that neat My object

[CodedFire]

@RD: Any book ive used the learn vb is much the same. Its not that its bad i just find that the way they teach C# is better and should be applied to VB. Im glad i started to learn both because although they are syntaticly different they are much the same functionally and i get to learn to different views on how the framewrok can be thought!

[Shaggy Hiker]

The difference may be due to lots of C# programmers coming from C++, and the writers are the fools who think they can make a buck by writing a textbook (Does this include one of the admins here?). Coming from a C++ background, I would expect a different approach than coming to VB either from nothing, or from VB6. Those coming from VB6 would be coming from non-OO to OO, so that might be the issue that made the biggest impact on them. Coming from C++ to C# would be moving from OO to OO, so they might be showing the similarities more than the differences.

Just a wild ass guess, though.

[CodedFire]

Actually come to think of it that doesnt sound too far off. I mean if you read Accelarated C++ by keoing and Moo. Their would be great similarities between this style of learning and the style presented in the C# books. The only thing is this style of writing is fundementally flawed.

Yes you can write larger programs quicker but because you were taught the implementation without the theory of any given piece of code you can only apply it in the context of which you first learned it.

That being said the best refrences i have come across yet have to be Wrox. Although their books can be huge they are written very thoughtfully and are well rounded!