Re: VB6 vs VB .Net

From: Bob O`Bob (filterbob_at_yahoogroups.com)
Date: 02/25/04 

Date: Tue, 24 Feb 2004 21:49:12 -0800

Ian Bayly wrote:
>
> As a long time user of VB (I actually have manuals which came with VB in
> those days), those that know more about these things than I do, tell me I
> should upgrade from VB6 to VB .Net.
> I have no interest or need to be involved with any web applications.
>
> Should I upgrade Yes/No?

Maybe change, but not "upgrade". Certainly not to VB.Net

VB6 has a limited future potential, that's for sure.

But there's just about zero evidence that VB.Net has any future at all
outside of scripting Active Server Pages. It's pretty much only *this month*,
after 3+ years of yammering on about webservice this and framework that, the
dotnet sycophant magazines and forums have finally started publishing articles
about "winforms" applications. A dozen or so of us went up to Redmond, at the
invitation of the VB and VS teams, and practically BEGGED for the resources to
generate those kinds of articles THREE YEARS AGO.

I recommend sticking with VB6 for as long as it serves your needs, then when
it doesn't any more, switch to anything else, *anything at all* other than VB.Net
Some VB experts have switched to Java, some to Delphi, some to C#, each of which
appears to have much a brighter future than VB.anything
Maybe, just *maybe*, someone up there will come to their senses and realize
that the golden-egg-goose of Classic VB isn't necessarily quite dead yet.
(hopefully before the dotbet scourge kills MS Office)
But a few backward-looking too-little-too-late features in "whidbey" are
more of a slap in the face than any real showing of respect.
It's about as if some people on the opposite side of a wide raging river
built *part* of a bridge *from their side* about 10% (or even 90%) across.
How much would that help you cross?

And there's plenty of reason to believe they'll abandon it all over again
if the marketoons decide the wind is blowing another way.

        Bob 

-- 
looking for work again  <http://obob.com/bob/resume/>

Relevant Pages

  • Re: Visual Basic.net
    ... Anyone evaluating your judgement and assertion as to whether VB6 is harder to ... However, if we switch, why not use Java? ... You've yet to address my concrete objections, ... >> VB.CLASSIC is dead? ...
    (comp.lang.basic.visual.misc)
  • Moving from VB6 to dot net
    ... Would anyone be able to offer any unbiased thoughts or advice on reasons to ... The stuff we use VB6 for is pretty simple compared to what ... to the central database etc. ... simple software for a smallish company, who made the switch, if so how easy ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Should Access VBA programmer move to VB .NET?
    ... Additionally, VB6 can compile to ... > generated by compiling VBA within Access and the 'native code' that you ... Please clarify. ... > upgrade hardware or software only when the benefits are obvious. ...
    (microsoft.public.vb.general.discussion)
  • Re: QUESTION: Jet Engine Database Sizes???
    ... The upgrade wizard puts "TODO" comments every 5 to 20 lines about something that has to be manually converted or rewritten, especially if you use the Windows API or graphics functions, so you have to rewrite the application to convert it to dotnet. ... If you are going down the route of upgrading a VB6 app to .NET, then the first thing you really should do is run the upgrade advisor on the VB6 code. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB5.0 to VB6.0, And Access2000 Compability
    ... > I feel getting access to Replaceand Splitis well worth the time to ... > Besides all the wonders and glory that was VB5, VB6 is an upgrade and ... > are many subtle differences between it and VB5 as Bob eluded to. ... What is more important are features in VB6 not present in VB5 that you CAN'T ...
    (microsoft.public.vb.general.discussion)