|
|
|
SSC Rookie
 
Group: General Forum Members
Last Login: Yesterday @ 3:12 AM
Points: 35,
Visits: 140
|
|
Maybe this will help: http://aspalliance.com/625
Personally, I'm a VB.net guy. If I'm honest, it is because for a few years I dropped out of the developer scene (working with TSQL and PL/SQL), .net sort of snook up on me. Now I'm getting back into it, I chose VB.net out of pure preference of the styles. I am however, quickly learning this is a mistake. It would appear the world is leading towards C#, and I can see VB.net being phased out (or at least send back to the "this is a learning language" days). All the jobs I see are for C# developers.
Lee
|
|
|
|
|
Grasshopper
Group: General Forum Members
Last Login: Thursday, November 19, 2009 7:52 AM
Points: 13,
Visits: 48
|
|
I've been using VB6 for sometime and recently started looking into VB.NET.
I think the reason people prefer C# is that (like someone posted), there is this general elitist syndrome from people who code with C++/Java concernig VB programmers and the same thing has translated into the .NET languages.
|
|
|
|
|
SSC Veteran
Group: General Forum Members
Last Login: Today @ 4:03 AM
Points: 244,
Visits: 628
|
|
I moved from a VB shop to a C# shop a few years ago and after the initial pain of having to learn the syntax, I'd say that there's little to choose between the two. (That said, I do miss the "Using" statement in VB  ). Now that I've been using C# for a while, I have to dig the book out whenever I switch back to VB.
Probably the biggest thing to learn in .Net is the framework, and this is the same in both languages.
|
|
|
|
|
SSC Journeyman
Group: General Forum Members
Last Login: Friday, February 26, 2010 1:38 AM
Points: 75,
Visits: 304
|
|
I've been using VB6 for many years and moved over to .NET about 3 or so years ago. I mostly program in VB.NET but on occasion tinker with C#. The one thing I love about VB.NET and the 3.5 Framework is XML literals! If you work with XML on a regular basis then VB.NET makes life so much easier than C# (in my opinion). As far as I'm aware this feature will remain VB.NET only!
I think there a lot of C# people who look down on VB.NET as being an inferior language but I think any real developer out there knows that each language has its Pros and Cons, and at the end of the day, is it not all about getting the job done on time with the least amount of hassle?
|
|
|
|
|
Forum Newbie
Group: General Forum Members
Last Login: Friday, November 13, 2009 7:32 AM
Points: 1,
Visits: 5
|
|
I started programming about 2 years ago using classic asp in web applications and am now using vb.NET in software development having had a period of doing web development in VB.NET in the middle. Of course because of the small amount of experience, I know no other than to use VB but have seen some projects using c# and it resembles slightly the java I used back in my degree and also javascript. It is slightly intimidating because of the lack of understanding I have for the syntax.
There is something about c# that captures me and is persuading me to learn it, I'm not sure if the drive behind this is personal preference or career prospect orientated (more likely the latter). My question is shall I become a more fluent vb programmer first and forget about c# for now or shall I start learning the syntax now even though I'm 10% of the way in to learning VB.NET (with WPF)???
|
|
|
|
|
Right there with Babe
Group: General Forum Members
Last Login: Monday, March 15, 2010 7:16 AM
Points: 720,
Visits: 4,809
|
|
For me C# is easier because I was in C++/Java development, but as Flo said there is no functional difference between C# and VB.NET.
-------------------------------------------------------------
"It takes 15 minutes to learn the game and a lifetime to master"
"Share your knowledge. It's a way to achieve immortality."
|
|
|
|
|
SSC Veteran
Group: General Forum Members
Last Login: Yesterday @ 8:18 AM
Points: 204,
Visits: 559
|
|
Being a .NET dev for 5 years, at last, something I can talk about!
Anyway, are we talking about the language or the development environment?
If it's the former, I'm surprised no-one's pointed out both languages compile to the same intermediate language, so it'll depend on whether you prefer semi-colons and curly braces, or underscores and full english words. Just to complicate things, in the IDE there's such a thing as auto-completed, so you don't even need to write the full words out anyway.
If it's the latter, then there's not much of a difference either. Back in the .NET 1 days, I preferred C# because it was the only language that supported XML comments/documentation - but even that's now gone.
Paul
|
|
|
|
|
Forum Newbie
Group: General Forum Members
Last Login: Friday, November 13, 2009 7:15 AM
Points: 1,
Visits: 6
|
|
I think VB.NET is seen as the easiest migration route from VB6, fair enough.
However the primary thing you are attempting to do is move to an new programming paradigm and sometimes forcing developers into using a new paradigm assists with the shift in thinking as it is "less easy" to fallback to what worked before.
Using C# also means that languages like Java, c, c++ are more identifiable and less scary to approach.
C# is not as verbose and more naturally integrates newer language constructs without falling back on Kludgey syntax like AddressOf stuff.
|
|
|
|
|
SSC-Enthusiastic
Group: General Forum Members
Last Login: Today @ 5:34 AM
Points: 146,
Visits: 609
|
|
If it's the former, I'm surprised no-one's pointed out both languages compile to the same intermediate language
Wasn't it mentioned in the original article?
|
|
|
|
|
SSCommitted
Group: General Forum Members
Last Login: Today @ 6:23 AM
Points: 1,718,
Visits: 379
|
|
Originally, the VB.NET team tried to make it have all the equivalent features of C#. In my opinion this was losing the power of the differences of use. It was a good thing that VB gained proper Object Oriented language constructs and a better error management facility (exceptions) but was in danger of becoming a C# clone with Begin...End instead to {...}.
That was up to and including .NET 2. however since then it appears the VB.NET team have really understood that VB.NET was the RAD tool of preference for Windows development.
C# gained designers from the VB world and VB.NET gained a raft of language features from C# (origins of most features can be found elsewhere but in the context of this discussion I am excluding this information).
I spent a long time working in teams comprised of C++/COM developers and VB developers. The differences in the features of the languages was celebrated and still should be in the C#/VB.NET world.
The right tool for the right job!!!
Hopefully someone thinks of me as a right tool 
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
|
|
|
|
