C# vs VB.NET
-
I'm sure this has been asked many times .... I have a potential customer that is currently a has a team of VB programmers. This team is looking at migrating to .NET. I have usggested to them that C# would be the way forward. How does the .NET community regard VB.NET versus C# ? My view is purely of a snob, and years of C and C++ developement. Does anyone have any convincing arguments, of C# over VB.NET. Currently my only argument is that C# is a more professional language, and has been designed specifically for the .NET environment. Any help ?
-
I'm sure this has been asked many times .... I have a potential customer that is currently a has a team of VB programmers. This team is looking at migrating to .NET. I have usggested to them that C# would be the way forward. How does the .NET community regard VB.NET versus C# ? My view is purely of a snob, and years of C and C++ developement. Does anyone have any convincing arguments, of C# over VB.NET. Currently my only argument is that C# is a more professional language, and has been designed specifically for the .NET environment. Any help ?
Two differences I know about: C# supports XML generated documentation of your comment-tagged source code, which VB does not. IMHO, this is a significant advantage. I've been playing around with NDoc which creates instant help references for your code. It's great! Secondly (and I might be wrong here) C# is now a recognized language supported by a standards committee, whereas I think VB is simply whatever Microsoft wants to do with it. Marc Help! I'm an AI running around in someone's f*cked up universe simulator.
-
I'm sure this has been asked many times .... I have a potential customer that is currently a has a team of VB programmers. This team is looking at migrating to .NET. I have usggested to them that C# would be the way forward. How does the .NET community regard VB.NET versus C# ? My view is purely of a snob, and years of C and C++ developement. Does anyone have any convincing arguments, of C# over VB.NET. Currently my only argument is that C# is a more professional language, and has been designed specifically for the .NET environment. Any help ?
What I have heard/read there is no very big differ between vb and c#. However I have not done anything with c#, so I might as well be wrong. But if the team has knowledge of old vb, why should they abandon it? vb.net is quite familiar to one who has programmed with old vb. Maybe familiarity would help to learn new ropes? I would really like to know, if there is something very different between vb.net and c#. best regards Tuukka