VB6 vs VB.Net

[Alex]

I'm thinking of brushing up on my VB skills...

I currently own VB6 but VB.NET seems to have changed a lot of stuff...

I was wondering whether its worth it for me to buy a VB6 book and learn from there or invest in VB.NET and a book for that too instead...

 

[Bulldog13]

They are pretty different. I d just go straight to VB.NET .

 

[torpid]

Originally posted by: Bulldog13
They are pretty different. I d just go straight to VB.NET .

Agreed.

 

[Apathetic]

The ONLY similarity between VB6 and VB.NET is the name.

Dave

 

[FrustratedUser]

Originally posted by: Apathetic
The ONLY similarity between VB6 and VB.NET is the name.

Dave

The syntax must be same right?

 

[Alex]

Originally posted by: Apathetic
The ONLY similarity between VB6 and VB.NET is the name.

Dave

i beg to differ... i heard they are completely different and for one i know that you can't create control arrays as easily in VB.NET as in VB6...

 

[torpid]

Originally posted by: franguinho

Originally posted by: Apathetic
The ONLY similarity between VB6 and VB.NET is the name.

Dave

i beg to differ... i heard they are completely different and for one i know that you can't create control arrays as easily in VB.NET as in VB6...

If by not as easily you mean that control arrays no longer need to exist but you can get the same functionality in a significantly more simple and straightforward fashion, yes.

http://msdn.microsoft.com/library/defau...ontrolarraychangesinvisualbasicnet.asp

 

[sourceninja]

If you going to learn vb.net you should just jump to C#. VB.NET and C# both "compile" down to the same CLR, but with C# you dont have to deal with the crappy hacks MS used to keep vb alive. C# was written as the language for .NET. VB.net was added because of public outcry, but C# is very similar to VB imho. The moral? Learn C#, you will be happier.

 

[torpid]

Originally posted by: sourceninja
If you going to learn vb.net you should just jump to C#. VB.NET and C# both "compile" down to the same CLR, but with C# you dont have to deal with the crappy hacks MS used to keep vb alive. C# was written as the language for .NET. VB.net was added because of public outcry, but C# is very similar to VB imho. The moral? Learn C#, you will be happier.

There are only a few minor differences in actual functionality. VB.net has some things I actually miss in C# and vice versa. The guy asked whether he should brush up on VB or go to VB.net. Does it really sound like he wants to learn an entire set of new syntax?

 

[sourceninja]

Well, from my exp with vb6 and .net it is almost an entire new syntax that has to be learned anyways. But its all in personal preference. Personally, I would rather work in ruby, but sometimes I'm required to use .NET. When that happens, I use C#. I think its a lot easier to work with then VB.NET.

 

[Alex]

thx for the feedback... i guess i can try out C#... i took some C programming stuff in college and i don't remember it all but i'm sure it'll slowly come back to me!

 

[royaldank]

I would reccomend jumping into .NET 2.0. I haven't actually seen the changes in VB.NET with the new framework and Vis. Sutdio but I know ASP.NET 2.0 appears to be much better than the first release.