Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Moving to .Net - C# or VB?
Message
From
21/06/2010 12:08:13
 
 
To
21/06/2010 11:29:03
General information
Forum:
Visual FoxPro
Category:
Other
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows 7
Network:
Windows 2003 Server
Database:
Visual FoxPro
Application:
Desktop
Miscellaneous
Thread ID:
01469892
Message ID:
01469929
Views:
189
>I (and a colleague) are finally embarking on the move to .Net.
>
>We have decided to follow the MCTS -> MCPD paths and gradually get qualified (my first ever qualification in IT since I am 100% self taught!)
>
>But we can't decide if we should go VB.Net or C#.Net, We are a vertical market developer, and currently use VFP9 desktop apps with VFP back end and an ASP.Net (VB Script) web interface.
>
>I know VB syntax would be easier to learn and I did a little VB years ago and the web stuff is currently VB, but are we then just learning another dying language? (don't jump on me that VFP's not dead - I LOVE the Fox and will use it as long as possible, but it is dying). Is C# worth the steeper initial learning curve and will it's very difference stop us getting the two syntax confused?
>
>Any thoughts welcome.

I'd go with the one you are most comfortable with - which sounds like VB in this case.
From a language POV the differences between VB and C# are getting less with each version.
Interesting wider perspective here tho (that may raise a few hackles :-} ) :
http://www.codeproject.com/kb/dotnet/CSharpVersusVB.aspx

Snip:

1.80% of C# programmers are good, while 80% of VB programmers are not good. This is not to say that everyone who programs in VB is less skilled than everyone who programs in C#. This is to say that:
a.the VB syntax and semantics is designed to attract less skilled programmers and, in combination with other factors examined above, this has created a culture that is populated with less skilled programmers.
b.and because VB syntax and semantics make it more difficult to avoid common programming errors and hence to program well.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform