VB 6 and .Net Comparison

Question

1.00/5 (1 vote)

See more:

I have a project to develop with 15 days. So, I am think which one to select, VB6 or VS 2010.
I need a comparison between VB 6 and .Net for this case.

Posted 18-May-13 17:00pm

AbinashVS

Add a Solution

2 solutions

Solution 2

VB6 is bad not just because it is old. Many even much older things are quite good.

It was "obsolete" even before it was introduced to market. The presence of its legacy is the real curse of many software teams where the leader did not have elementary vision in the past, one of the most massive disasters. Not just considering, but even playing with the idea of considering it is just ridiculous. Life is too short to waste it for digging in trash.

—SA

Posted 18-May-13 17:41pm

Sergey Alexandrovich Kryukov

Updated 18-May-13 17:42pm

v2

Comments

AbinashVS 18-May-13 23:58pm

Ok, I understood. What is its major drawback?

Sergey Alexandrovich Kryukov 19-May-13 0:36am

How can you imagine the answer? :-) Everything is bad...
—SA

AbinashVS 19-May-13 12:56pm

Not like that I have taken everything in VB6 is bad. But I wanted to know what was its drawback? I know this much that it supports only 32 bit. At that time there was also Delphi which was much better than VB6.

Sergey Alexandrovich Kryukov 19-May-13 13:45pm

Delphi is almost perfect, the only drawback is the lack of standardization of the language. It does some drawbacks though.

As to VB6, discussing separate "drawback" is just not serious, it would take enormous time, not a productive activity. You see, it is not even supposed to be fully-functional, not everything can be done, in principle. And no OOP. Let me be straight: the language was originally created as a language for lamers. I don't think the creators of language expected such popularity. It was a tool to give lamer some toy in hands, so they would distract adult developer less (and would not successfully grow into real competitors)... At least it looks like that. :-)

—SA

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Ron Beyer · Accepted Answer · 2013-05-18T17:24:00

Solution 1

VB6 is old tech, I would use newer technology. However, that being said, if you only have 15 days, now is not the time to learn something new...

If you want a comparison, then do a google search, should be easy to find.

Posted 18-May-13 17:24pm

Ron Beyer

Comments

AbinashVS 18-May-13 23:32pm

Thanks,
I am thinking that now I will do it in VB6 and later I will go for .Net. So that I can also test the Migration tool. Any Idea about the VB6 to .Net migration.

Sergey Alexandrovich Kryukov 18-May-13 23:43pm

The problem with this answer: it looks like VB6 was once good and became obsolete. Not true. Please see my answer.
—SA

Ron Beyer 18-May-13 23:48pm

Don't read too deep into it, I wasn't trying to say that VB6 (or even .NET) was ever "good". I was giving the answer between the two choices. If he were to ask what language without giving the two choices, I would have gone with C#. I used to be a VB programmer and moved to C# for much of the reasons you gave below. However, that being said, even VB6 had its place, mostly in application extensions in the form of scripting (aka VBA) or even shell scripting.

Sergey Alexandrovich Kryukov 18-May-13 23:54pm

I agree, but this is the impression...

As to C#... Of course, C# is decent well standardized language, and the problem of VB.NET is that it will hardly be ever standardized and usually perceived by community as not "professional" (from the pure standpoint of real-life social settings, no matter how good this language can actually be). Even if such vision is subjective (not only), this is very important practical reason to prefer C#, event if it has few apparent drawbacks...

OP just did not ask about C#, but I would note that, even developing in VB.NET on regular basis need at least some knowledge of C#, at least to be able to communicate productively with the members of .NET community, get some help, and the like...

—SA