VB.net and Visual basic

[JuniorOnline]

Hi All,

For someone who wants to do vb.net who never did OOP - do they need to learn VB on its own and then apply it within the vb.net evironment? or is vb.net completely different?

i am trying to find some info on the web on vb.net as a language..the majority of the tutorials are on how to use ASP.net and nothing on vb the language itself.

i think am getting very confused.

thanks
Tala

[essive]

You certainly do not need to learn VB first before VB.NET. In fact, I would not recommend it. But, a couple of things first:
- Remember that ASP.NET is the blending of server centric web delivery with the .NET platform. Thus, you can use any .NET language (C#, VB.NET, J#, JScript.NET, etc) to build your dynamic web pages and server side code.
- The language constructs for VB.NET although similar are not quite the same as VB.

I would suggest going to the Microsoft MSDN site to get your tutorials. The best thing about VB.NET is that it is free and you do not need Visual Studio to learn it (although it helps). Here is a great starting point:
http://msdn.microsoft.com/vbasic/ref...c/default.aspx

To start using VB.NET free - go to:
http://msdn.microsoft.com/netframewo...s/default.aspx
to download the framework

If you want to develop full end-user applications then buy Visual Studio. However, if you are interested in web development ASP.NET Web Matrix is free and allows you to use the VB.NET language.

[mccreath]

I would go further and say its better NOT to know VB before using VB.Net!

VB has a lot of bad elements which cause bad practices that can be transferred to VB.Net programming.

Infact, I would recommend not using VB.Net but use C# .Net which in my mind is a better language.

[JuniorOnline]

thanks guys.. things are making more sense now for me.. i will avoid VB and start on the 2 links provided. :)

[rwil02]

Originally Posted by mccreath

I would go further and say its better NOT to know VB before using VB.Net!

VB has a lot of bad elements which cause bad practices that can be transferred to VB.Net programming.

Infact, I would recommend not using VB.Net but use C# .Net which in my mind is a better language.

In fact, I'm a VB 6.0 developer (from Access/VBA) nd when I shifted to .NET, I followed the advice of a Microsoft programmer and switched to C#. Not because it was any better, but because "it helps you break all the bad habits you learn in VB" All the things that are not appropriate ways of thinking in .NET.

[Vectorman211]

I agree, if someone held a gun to my head and made me use MS for my server solution I would use C# as well :D