• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1689
  • Last Modified:

VB6.0 vs vb.net

What are the differences and simalarities between vb 6.0 and vb.net. Also if i was to migrate from vb6.0 to vb.net what advantages would i get and the difficulties(I know i would have to learn new comannads in vb.net asi only use vb 6.0 but i mean advantages the software ect woyuld give me).
5 Solutions
fishmanfishmanAuthor Commented:
i can raisethe points if you feel it is a big question to answer!
There are SUPREME Advantages of VB.NET, i dont know where to start so you'll just have to take the word of about 1,000 or so people on here.  There are alota things that are much better, for one is the Interop Services, and the fact that commands are alot easier to remember and compiling is easier and... *benifit overload*... Its just alot easier to program, 5 Lines VB.NET = 40 Lines VB6


1) the basic Language syntax is almost the same.

2) The IDE is very similar, though there are some significant differences.


1) .NET is 100% Object Oriented, and everything (Yes, EVERYTHING) in .NET is an Object.  The maning of this is that the .NET programming paradigm (the basic underlying principles) is very much different from Visual Basic 6.0.  So much so, that you should NOT attempt to 'upgrade' any existing Visual Basic 6.0 program to .NET.

2) ADO.NET is much more than simply an upgrade to ADO.

3) Database access is greatly improved, and database connections can be managed directly from the IDE (if you are using SQL Server)

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Having programmed in VB6 for along time, I have switched to .Net A year ago. And VB.NET is far superior to VB6.

To mention a few,

VB.NET is totally OO (inheritence polymorfism encapsulation), Meaning it is much easier to reuse your code and to build powerfull applications) (Inheritence rules !!!).
It is much easier to create windows services/ web apps/ console applications/ usercontrols)
as mentioned by darkpriest, less code is often needed in .NET than in VB6. the .net framework incorporates a lot of predifined stuff that you had to code in VB6 yourself.
Things like filewatchers (a class that will let you monitor files/directories)

some pitfalls

ADO.net doesn't resemble the old ADO at all, there are no recondsets anymore and it is a disconnected model, This took me the most time to get used to (but you will eventually :))
The datagrid although it is fully customizable it takes a lot more code than it used to (my advice, buy a datagrid from componentone or infragistics)
There are no control arrays anymore (you have to build them yourself)

If you need more specific info, just ask
Bob LearnedCommented:
After stepping through the door into the magical world of VB.NET, you will be blinded by the wild array of new things, and you will be totally disoriented for a while.  Many of those things that you could do in your sleep in VB6 have changed, and you will have to start on a learning curve to do somethings differently.  At first, most old VB6 developers resist, and think about migration.  While this sounds enticing, after a while, you will get disgruntled over the mess that the migration tools make out of it.  Then, if you are smart, you will leave your old habits and knowledge behind you, and move ahead into the full-featured .NET Framework, and learn it's magic and also it's strange behaviors.

As pointed out so eloquently by Ronald, ADO.NET is a major player in a lot of software development, and has gone through an extreme make-over.  Some impressions are that it is good, and others are that it is 10 times easier to do in VB6.  My impression is that it is just different--not better, not worse--just different.

I have tried to make it a point to learn such new concepts as WMI, ActiveDirectory, Regular Expressions, and GDI+, since they are integral to my work, and the tools in .NET are pretty awesome.  Although, I think that GDI+ needs to grow a little more, as it still feels like it is still in its infancy.

I know not as indepth as other answers but as someone who once made the move over 12 months ago.

VB .Net has a faster and easier workflow.
VB .Net shares alot of common ground with C# and others because of .NET making it easier to jump between language and still get the application running.

If you move directly across do not expect everything to work, infact assume the worst and create a new project. I found this the simplest solution. Then simply start to migrate in small parts of your project fixing what you need. You will run into some systax errors, and certainly alot of database problems. There are also alot more features visually and techincally available to you, so once you have everything in and working (some effort required) consider if you need any new or upgraded features.

VB .NET allows you to easily create ASP .NET applications once you get to grips with some basic concepts. The biggest headache you will have are the your old thinkings. Try and forget them as it will lead to bad programming within .NET. simply consider this as a complete port to a new language and essentially a new platform and all should be good. After that all I can say is best of luck.

Featured Post

Vote for the Most Valuable Expert

It’s time to recognize experts that go above and beyond with helpful solutions and engagement on site. Choose from the top experts in the Hall of Fame or on the right rail of your favorite topic page. Look for the blue “Nominate” button on their profile to vote.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now