[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

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

VB vs VB.net

Dear all,

Our company is considering moving from VB to VB.net.  Could someone point to a convincing article that VB.net is much better than VB?

Thanks in advance.

5 Solutions
Hi vbTiger
I don't think any article is now required to convince anyone.
The simple reason is, there's no way out.
Of course one can argue about the benefits of .NET but even if you are not convinced you'll need to move because vb6 is now obsolete (or surely going to be soon).

If you plan to migrate your existing vb6 application to .NET one might require to sit and think and in that case probably one might suggest against going for .NET
But for new developments there's no other way, (soon) you won't find vb6 programmers, you won't find any support and I wonder if you could even get the Visual Studio 6 SDK.
So no way out...

Éric MoreauSenior .Net ConsultantCommented:
VB6 is no more actively supported! No more service packs are announced.
VB.NET supports different syntaxes and different methods to accomplish something. Creating controls is far easier and more doable in VB.NET.
In addition, the graphics are very advanced. For instance, RGB colors have a new parameter called alpha, specifying the opacity...
In general, developing vb6 is riskier and more difficult. In vb6 you can not turn off auto-casting which can cause hidden errors. Also, in VB.NET you can use two different debugging strategies. VB6 does not support the famous "Try" block. This a major disadvantage to Java, but it is compensated in VB.NET.
The NET languages try to find a common ground between all languages (especially Java), so that you will be to update your software in the future. If you won't upgrade now, the common programming languages change further, and at a time you won't be able to upgrade and have to pay to create a new software from scratch...
I would say that the argument is the same as moving from DOS to Windows, or from vinyl records to CDs

If DOS is doing EVERYTHING you need, then you probably don't need to change.  However, understand that the risks grow greater and greater as time moves on because the "parts" you need for any repairs (like a record needle or DOS patch) become harder and harder to get and may even not exist.

All that said, there is still a strong VB6 base out there and I perceive that it will be still going for another 5 years, partly because the learning curve on DotNet is much greater than from VB5 to VB6 or even VB3 to VB6.  Although the concepts still apply, the implementation often changes.

One more thing, like most advanced tools (CD versus vinyl record), the technology is much better in many areas.  Although I wouldn't jump ship on a working application, I would seriously look into upgrading while you're NOT in crisis mode, just to see if it's feasible.  If not, keep the VB6 stuff and slowly start rebuilding a parallel application in VB.Net.

Aside from the company, YOU don't want to fall too far behind the technology curve or you will become obsolete and the company will likely not care about throwing you away when the time comes.

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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