Not meant to ignite a language war, so if mods can remove such posts - please, it's meant as a fairly constructive discussion on the merits of one, the other, or both.
Discuss:
Printable View
Not meant to ignite a language war, so if mods can remove such posts - please, it's meant as a fairly constructive discussion on the merits of one, the other, or both.
Discuss:
Use both as the framework is common. If you know one the other is not very hard to pickup. You use the right tool for each and every job.
If you are coming from a VB 6 ground then I would suggest learning C# first and then turning on to VB.NET. This is just because when you move over to .NET and you are still using VB then you tend to do things in the same way as we used to do in VB 6, which is not good. We tend to forget that there are so many functionalities added to .NET. So if you learn C# (as it is a new language) you will also lern how to take advantage of what .NET Framwework has in store for us.
To me both C# and VB.NET are same because both of them target same Base Class Libraries. It is just the matter of expertise that you have. Some people will prefer working in VB.NET and some in C# but mostly the underlying MSIL is same. There is nothing that cannot be done in VB and can be done only in C# as far as I know.
Also with .NET 2.0 VB has become CLS Compliant so the advantage of C# being CLS compliant in 1.1 environment has also been taken care of in .NET 2.0.
To me whether you code in C# or VB.NET you are still a .NET programmer and can easily move to the other .NET language with ease.
It's easier to learn VB.NET if you are familiar with VB6 and it's easier to learn VC# if you are familiar with java and C++.
It really depends on you. and just like Shuja Ali said "You are a .NET programmer" anyway so it doesn't really matter.
I'm not sure about the differences between the languages in .NET2 - I guess C# will always have the unmanaged code advantage (not recommended to use) - but it'd be the best if you learn both, since you can use all .net languages in a single solution
Both. My path: VB6 -> VB.NET -> C#
And you might as well get ASP.NET under your belt if you have that option. It's the future of development.