Visual Basic 6.0 vs Visual Basic .NET

[darkritual]

Hello everyone,

Yesterday, i started learning about VB6 and would like to know if VB.NET is a simply library of VB6. ( Just like jQuery and JavaScript )

If not, should i learn VB.NET instead of VB6 ?

Thanks

[.paul.]

VB.Net superceded VB6 in 2002.
Since then there have been 6 versions of VB.

I'd recommend learning VB.Net:

www.homeandlearn.co.uk

[jmcilhinney]

The relationship between VB6 and VB.NET is quite unlike that between JavaScript and jQuery. It's more akin to that between C and C++. Visual Basic was a Rapid Application Development (RAD) tool for building GUI applications with a programming language that was basically (and actually, I think) a superset of the original BASIC language. That tool and language evolved through various versions up to VB6.

At that point, Microsoft introduced the .NET platform, which had, as one of its goals, to eradicate some of the issues associated with COM-based programming. The two primary programming languages for the .NET platform are C# and VB. C# is based on the syntax of C/C++ (braces, semicolons, etc) and resembles Java in many ways. VB.NET (now just called VB) is based on the syntax of VB6 and earlier. Just as C# syntax is based on C but C# is a different language to C, so VB.NET is based on but different from VB6. The first version of VB.NET was also known as VB7 but most people who have experience with VB.NET consider it a different language to VB6, not just a simple evolution to a new version of the same language. There are many similarities between the two but there are many differences too.

While there's also a big middle ground, there is a bit of friction between those dedicated to the .NET platform and those who staunchly cling to VB6. In the interests of full disclosure, I will say that I used VB6 for a sum total of one weekend and hated it (I was a C++ developer at the time) but, when I tried it about two years later, I took to VB.NET very quickly and easily. Being as objective as possible though, I would recommend to any new developer to learn VB.NET in preference to VB6. The .NET platform is over 10 years old now and the tools and languages are in their sixth iteration, so VB6 is really old now and Microsoft no longer officially supports it. VB6 does have one or two advantages but VB.NET has many more. I can't see any reason for a new developer to learn such an out-dated language/toolset as VB6 unless they need to for a specific project.

[dday9]

This discussion has been going on since vb.net came out. Plain and simple, you'll have die hard vb6 fans and then those who've embraced the newer technology and have took on vb.net. In vb.net you can still use the vb6 functions like MsgBox, Mid, etc. so event if you wanted to use old functions you can. If I were in your shoes, and you're trying to get into the programming field, learn vb.net and don't look back. You won't regret it.

Edit - But ask this question in the vb6 forum and see the different results you get.

[darkritual]

Wow, i had no clue VB6 was this old.

I guess I'll start over and learn VB.NET.

[darkritual]

Well, that's kind of stupid but, i read the exercise entitled : "What is visual basic" after skipping it the first time and the instructor clearly said "We will learn more about the .NET framework..".

So, i didn't waste my time after all.

[Niya]

Having used both VB6 and VB.Net, I'd state it plain and simple: Don't waste any more time than you have to with VB6. VB.Net is a 100x better.

[ident]

Don't you mean 1000x better? I started programming in vb6 in 97, and made the switch around 2003. A few times i have had to fire up the VB6 IDE and it was a nasty experience each time. If you want to hear it there is many people who will tell you all is well in the VB6 camp. VB6 does not exist to Microsoft. They have made this clear for a long time now. I think the final dropping point will be Windows 10. If you wish for your application to live a long cycle then dont write it in VB6 (Ignoring it's Support Lifecycle). You also must remember VB6 applications on Vista/W7 etc run on a compatibility layer. This layer is nice face value but bloats the OS. So yes Microsoft would want to cut this clutter out.

I know i have not listed any A V's B answers. I dont feel it's needed. Don't bother with VB6 is the simple answer.

[Niya]

Don't you mean 1000x better?...

I didn't want to drive the knife of truth too deeply

[ident]

I remember staying up till 6am with my x-mas copy of vb6 (1997 @ 13) writing a MSN Messenger flooder. The youthful joy's of send keys

[Niya]

Haha...I remember my first foray into Windows programming with VB2. I was so excited about the fact that BASIC could actually change file attributes and wrote a small program just to do that. Back in DOS, changing the attributes of files was something only gods can do and by gods I mean ASM/C programmers. Lowly BASIC programmers could only dream of doing that.

[kareninstructor]

The only reason for learning VB6 is if your job required it. This is what I did, learned just enough to assist in one project over a one month period back in 1999 and never touched it again. Best to become proficient in Visual Studio 2010 minimum and best to use Visual Studio 2012.

[.paul.]

Best to become proficient in Visual Studio 2010 minimum and best to use Visual Studio 2012.

I'd recommend 2008 minimum. I do most of my programming in vb2008, only using the higher versions when I need their features

[kareninstructor]

I'd recommend 2008 minimum. I do most of my programming in vb2008, only using the higher versions when I need their features

I agree, the only reason I did not mentioned VS2008 is because Microsoft page for downloading VB.NET 2008 Express is gone, they only have VS2008 paid version via a subscription now. Seems many want to get their feet wet with Express after seeing the price tag of the current release of VS.

[jmcilhinney]

I'd recommend 2008 minimum. I do most of my programming in vb2008, only using the higher versions when I need their features

There's really no point a new developer using anything earlier than 2012 other than for compatibility. VS 2012 can target any Framework from 2.0 to 4.5 so there's no issue with application compatibility. If you need other developers to be able to open your solutions then you need to have a version of VS that is compatible with theirs. That means that your version must be no later than their version. If your version is earlier than theirs then the solution will be upgraded to their version when they open it and they will then not be able to share their changes with you. The exception to that is that 2012 will not upgrade solutions created in 2010. A 2010 solution will open in 2012, allow you to edit it and then open in 2010 again.

As you're doing a course, you will almost certainly have to use the version that they prescribe. If you don't then any assignments you submit in the form of entire solutions will not be able to be opened for marking. If there are no restrictions then I would suggest using the newest version. Just be aware, though, that you may have to go back to an older version sometime in the future for compatibility with others. For instance, I work in 2012 all the time but, when I upload a solution to this site for a CodeBank thread or as a demo to fix a problem for someone else, I always use 2010 for compatibility. I'll sometimes use 2008 if I encounter someone stuck in the steam age like .paul. but I avoid it if possible.