Using VB6, should I go to VB Net?

[ildenizen]

Please forgive my very simplistic question.

I am using VB6, and have not even touched the surface of all I can do with it. However, I may have a VB net version available. But I do not want to install or use it if it does not provide me with some significant advantages. Does anyone know the basic differences between these versions? What should I be able to do with VB net that I can't do, or can't do easily with VB6?

Thanks for your patience!

 

[JohnYingling]

Be current? Especially ASP.Net.

http://www.VBCompare.com

Compare Code

 

[dilettante]

There is no simple answer to this question.

For the most part this shouldn't even be a question. There are few reasons to stay with VB6 at this point:
[ul][li]Bloated .Net runtime not widely predeployed[/li]
[li]New skills required because VB.Net is a large departure from classic MS Basics[/li]
[li]Older machines with limited resources tolerate VB6 better than .Net applications[/li]
[li].Net is a moving target, new versions every 2 years[/li][/ul]
The first issue diminishes a bit each day. The second should just be a matter of time. The third one is fading away. As for the last one, VB was just like this when it was current technology.

I'm not being negative about VB6, I use it myself and have barely explored the tip of the .Net iceberg. Reasons to stay are evaporating though.

Anyone else have reasons to stay with VB6?

 

[strongm]

I'd add another: it's still a bit of a pain automating unmanaged code applications (e.g Office) from VB.NET, particularly those that don't have comprehensive PIAs available