>IMO, many jump on the C# bandwagon because it has the letter "C" in it
What brings you to that opinion? There are a handful of reasons why I choose C# over VB.NET, and I've never learnt C or C++. Two major ones, not getting into technical differences like Kevin, would be the available documentation/resources and the fact that C# is an open standard. Meaning that the time I invest into learning C# should be eased by the resources and I could port code to other platforms using the C# standard.
What else does the C# standard mean to me? Since C# is a standard, which is based on other standards (C/C++) when VS.NET 2.0 comes out, I may need to adapt my code for new framework classes, but thats about it. With VB.NET, a proprietary language, it may... and probably will change a little bit. It has in the past, I don't see why it will stop now.
The last point is C# has some more power features than VB.NET, mostly, being able to run unmanaged code.
Because the differences are very trivial, I'd say its a completely personal decision based on what you already know. If you have expeierence with Java/C/C++ or VB then you should choose C# or VB.NET respectivley. If you don't have expeiernce with either, or, you don't care about learning something new, I'd say try C# because it does have those advantages.
Of course, when all is said in done, the real selling point will be if employers are specifically asking for C# or VB.NET developers as opposed to .NET developers (which is what I'm guessing Microsoft envisions). Based on the above advantages and how often reality never ends up as planned, I wouldn't be surprised if there was a demand for C# specifically.
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only