VB 6.0 Vs VB.Net

Hi i would like to know which one of you think that Vb6.0 is better than VB.net or VB.net better than Vb.6.0. I just want to know
Who is Participating?
PAQed with no points refunded (of 50)

Community Support Moderator
Ryan ChongCommented:
Definitely VB.net better than Vb.6.0!

Have a look at:
Advantages of Migrating from Visual Basic 6.0 to Visual Basic .NET
they both have their pro's and con's.

I like vb6 for desktop applications that can be deployed over a network. it seams that .Net won't run a desktop application from a network drive. If it can be done, which i am certain it can be, then it takes too much effort to get it running for all users correctly. .Net on the ohter hand is excellent for web applications. i have had a much easier time creating web apps that act and work like i really want them to. some things are easier to handle in .Net as oppesed to ASP. .Net also has alot more classes that make things alot easier to accomplish like working with processes. However .Net can also take alot more code to accomplish things that vb can accompish quite easy. I actually use both and decide what environment would be best for the application. I like VB6's IDE better because you can edit code on the fly by pausing the debugger. .Net doesn't allow that. It compiles then runs the application. in debug mode when you get an error it tells you where it is but you have to stop the application and then fix it and rerun.

Those are just a few notes, hope it helps.
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

I think you'll get as many different opinions as there are people who post a response. :)
What you need to be concerned about is "Which is the right tool for this particular job?"

As for me, I currently do the majority of my work in VB6.  That's only because that tool happens to be what is required for the job.  Eventually, we'll have to move to .NET simply because MS will stop supporting VB6.  Plus, if you're trying to market yourself as a programmer, it's good to keep the skills as current as possible.  :)

Take care.

having programmed extrensively in VB  (3,4,5,6) since 1995, and VB.NET (2001,2002,2003), there is almost no comparison.  I definitely prefer .NET to Classic VB by about 10 to 1.  I still have to work with VB 6 (and VBA in Excel and Access), due to customer constraints, but I greatly prefer .NET.

I used VB.net for a few months and what I found was that if you are doing Web based apps it's great because that's what it was designed to do best.  If your doing anything else it tends to be a more labor intensive language than vb6 and a lot more difficult to use, especially for simple stuff.
Also the above stated mention of editing the code on the fly while debbuging is a huge part of my dislike for .Net, if your the kind of person who does code in a very structured way, this will be only a minor inconvience but if you do code like most people, using the "Write and Try" method, this will be a huge frustrating problem.
jgarth, that statement is not true.  VB.NET was NOT designed primarily for the Web.  I have found the vb.NET is also a very good language to use to almost any type of application, and once you get into it, and understand that it is a different design methodology from that used by VB 6, then you will see that too.

Debug and Continue has been added back to VB.NET 2005.  

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.