Advantage of using VB.Net instead of VB 6.0

Dear All,

I need to develop a window application to run on WinXP.

As titled. How can I justify which developing tools to be used?

What is available in VB.Net, not in VB6.0 or vice versa.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Hi iecu

A large consideration would be Microsoft not supporting VB6 anymore. I know there is still a lot of information on the Web and in sites like this, but over time that will diminish as more people take up .Net or other languages.

As you are using XP, then the .Net framework is installed as part of the operating system.

If you decide to start your development now within VB6 I am sure it will be a very short time before you find yourself then coverting it over to VB.Net, so you are probably better to bite the bullet and start now.

As to specifics
 - VB.Net now being OOP where we can now do inheritance and all that good stuff
 - End to so called DLL hell
 - Data binding (this to me is a massive improvement)
 - Application blocks of code supplied by Microsoft that can be downloaded FOC
 - Langauge of choice C# / VB can now be easily combined within one solution as both use the same framework / IDE etc.
 - ... and many others

HTH :)

iecuAuthor Commented:
Hi cubixSoftware,

For the advantages you mentioned, what do you mean for data binding & the code can be downloaded FOC?

Could you further explore these?

Thanks a lot.

The following link explains Microsofts Patterns and Practices of which Application Blocks are one part of it. Basically they are .Net projects (including source code) that you then just include within you Solution and if you want you could simply amend them. They are there to save you from doing the repetative coding for each solution - like we always have to do a data access layer that is always the same

With regards data binding

Many controls can be bound to many different types of objects. We can bind still to datatables, data sets etc.  but now also bind to arrays, hash-tables, collections.

Data driven applications can be achieved in very few lines of code using controls such as combo boxes and especially datagrids. Below are some links that should take you through all these areas.,39026692,60116200p-39000929q,00.htm,39025945,60024693p-39000537q,00.htm

HTH :)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Visual Basic.NET

From novice to tech pro — start learning today.