Printable View
We use VB6 and SQL Server 2000 at work, but VB6 is outdated and SQL Server 2000 soon will be.
I've been reading up on VB 2005 at home but obviously I don't have much free time to play with it. I have the express edition of VB which stinks.
What I'm wondering is do you guys think I should learn VB 2005, or should I try to make the leap to C#?
If you have previous C, C++, VC++ experience or even Java you should go for C#. If your more comfortable with VB 6 then go for VB.NET as once you learn the framework the other languages of .NET are easy to pickup.
Quote:
Originally Posted by RobDog888
Sounds reasonable.
Go for C# anyway. VB.NET sucks.
/opinion
You make a good argument. However since I haven't even gotten into classes in VB I'm not sure I could understand them in C#.Quote:
Originally Posted by penagate
It's quite simple. And personally I get confused between VB.NET and VB6 sometimes whereas with C# it's a whole different syntax so it is easier to keep them separate in your mind.
Also the principles are the same in all .NET languages, but the keywords used in C# are more in line with other OOP languages.
Better argument?
Yes, but I'm not all that familiar with OOP principles. Yet. :bigyello:Quote:
Originally Posted by penagate
I skimmed over a bunch of OOP tutorials; most of them were dodgy, but this one seems quite good and suited for your needs:
http://dotnetjunkies.com/Tutorial/B1...775ACCD46.dcik
Bookmarked, I shall definitely read it.Quote:
Originally Posted by penagate
Learn Java, its a nice OOP language to start with. Last year in university we used a tool called BlueJ (with Java) that had a basic implementation of UML, so you could see how your classes related to each other, etc...
I suggest you learn C#. Even though you mention haven't worked with classes in VB6, as you gain experience all will come clear - and you'll be working with classes no matter which .NET language you choose. The company you work for might migrate to .NET, and they might choose VB.NET - and that should be a factor in your decision. However, once you have started learning C#, then later switching to VB.NET isn't difficult (and the opposite is true as well).
It is a matter of personal preference, of course, as to which one you will find more natural for you. The key is that they are both very similar, and both rely on the .NET framework classes to provide most of their functionality, and therefore you can choose one or the other and learn pretty much the same things as you progress.
I have been using both VB.NET and C# for almost six years and use them both since I have to use whatever the project is using. I prefer C#, and in my area, C# programmers are usually paid a little higher rate than VB.NET programmers. There is no logical reason for this that I have been able to find.
Regarding Java - it is also a good language to know. However, I suggest you check your local employment opportunities and pick a language that gives you the best chance at staying employed, and give you a path for job advancement.
Once you have experience with a good, currently "in demand" language (such as C#, VB.NET, Java, or whatever) you will find yourself looking at other languages to see what they have to offer, and maybe learning a few other languages over time. The Pragmatic Programmers (Dave Thomas and Andy Hunt) recommend learning a new language every year, and that is what I try to do - (at least I think it was them that made that recommendation).
Anyway - have fun.
As you are already familiar with VB learn VB.NET. Once you are comfortable with VB.NET it is simple to move to the other languages on offer (C#.NET, J#.NET etc).
Thanks for all the advice guys.
I think I'll probably go the VB.NET route because I'm new to the .NET framework and it may be easier to learn if I go with a language that's a bit more familiar. I'm very new to programming for a living; I've only been doing it about a year.