Re: VB6 vs VB .Net

From: Howard Kaikow (kaikow_at_standards.com)
Date: 02/25/04 

Date: Wed, 25 Feb 2004 02:18:50 -0500

I'm gradually going to convert all my VB and VBA into VB .NET.
I have no incentive to use other than "VB" until Office becomes fully
.NET-ized.
Once the VB/VBA is converted to .NET, I'll more easily migrate to C#,or
whatever, since the painful distinctions 'tween VB Forms and VBA Userforms
will, hopefully, be no more. 

-- 
http://www.standards.com/; See Howard Kaikow's web site.
"Bob O`Bob" <filterbob@yahoogroups.com> wrote in message
news:403C3758.507B@yahoogroups.com...
> 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: Why to use VBA?
    ... all I am saying is its time to start introducing new features in .net that will do the same thing VBA does and give the market time to accept it without dropping VBA as you said executives are conservative to change VBA! ... The fact is that VB.NET is sufficiently incompatible with the previous version of VB (VB6, from which VBA is derived) that for all practical purposes an upgrade wasn't possible, you had to rewrite the code more or less from scratch. ... The automated code converters provided by Microsoft were next to useless, and the fact that Microsoft went and changed lots of names of objects and properties meant that late-binding code wouldn't work without rewrite because it couldn't be automatically converted at all. ... Lots of people asked Microsoft what that reason was, with regard to that and dozens of other changes to the language. ...
    (microsoft.public.word.vba.general)
  • Re: ADP or MDB - which is a better front end for SQL Server?
    ... I have the same opinion about Longhorn and VBA under Access and Office: ... the lack of support for VB6 is not a big deal but ... > the support, but I have lived without the support for years already, I ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Help needed in using FSOs, TextStreams, etc. --- Code Review and Advice requested
    ... VB programmers still use VB6 or VBA. ... VB6 or VBA, you would do something about it from a business activity perspective. ... Microsoft about it in a professional manner, I would be open to writing something ...
    (microsoft.public.dotnet.languages.vb)
  • Re: VB or?
    ... I code in both VB6 and VB.Net on a daily basis and while they ... (or even C# if he wants to stay with a C-Like dialect). ... helpful pointers. ... Actually VBA is next on the "hit list". ...
    (microsoft.public.vb.general.discussion)
  • Re: VBA and VSTO
    ... Moving code to VB6 can't be simpler and I am sure that is the best way to go. ... .xla add-in at 3.9 Mb with all the non-code bits completely stripped out. ... But I don't think that will happen; too many people manage get things right in VBA, ... I don't know what you mean exactly with "I've built a compiler " but it makes me shiver. ...
    (microsoft.public.excel.programming)