Re: vb6 bcoming irrelevant?

Tech-Archive recommends: Fix windows errors by optimizing your registry



Most vendors don't typically continue to sell older versions of a product
line, especially since
mainstream support for the product has ended.

True, but most vendors are very concerned about backward compatibility to
protect their customers' investments.

Also, support for some very old versions of Windows ended years ago, but MS
still (quietly) sells licenses to many customers who chose not to move
ahead.

Assuming MS are not insane, they will realize that dragging horses to water
and trying to make them drink results in nothing more than angry thirsty
horses. The secret is to convince the horses that they are thirsty and
showing them where the water is.

I tried loading my VB6 body of work into VB.Net. There would be thousands
of things to fix - months of work. It's like moving to a different
language. If MS were to contemplate dropping VB6 backward compatibility in
Vista, there will be many thousands of angry thirsty horses - including some
very large corporate customers!

Nigel


"Paul Clement" <UseAdddressAtEndofMessage@xxxxxxxxxxxxxx> wrote in message
news:brc5b25t1val6681k7s7ipcco78qsd22cu@xxxxxxxxxx
On Mon, 10 Jul 2006 01:17:39 +0100, <Darren> wrote:

¤ The funny thing is that vb6 is becoming obsolete not because it is
¤ not good, or because it is not up for the job, but simply because
¤ no one can purchase it any more. In fact vb6 is currently more
¤ expensive 2nd hand on ebay than studio 2003/5 brand new.
¤ Would ms object if some one
¤ made it publically available? I simply can't understand ms's
¤ logic here? Do they think we should only use .net? this is stupid,
¤ they discontinue something good, this must be a wrong
¤ decision.
¤

Most vendors don't typically continue to sell older versions of a product
line, especially since
mainstream support for the product has ended.


Paul
~~~~
Microsoft MVP (Visual Basic)


.



Relevant Pages

  • Re: Fighting the Dark Side
    ... ¤> me a few days), the comfort level should be fine. ... IS a major learning curve. ... The transition from VB6 ... Then you get the usual knee-jerk responses of "it may be newer but why is it ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... Visual Basic.NET, maybe, not VB6, I'd still give the nod to VB6 by a good ... RAD advantage but suffer from an incomplete representation. ... Yep, that's a big difference and unfortunately the way Microsoft did things, ... ¤> more capable tool when .NET was released. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6 Error Handling
    ... ¤ has been and still is a group for VB6 and below. ... What I had in mind is only regarding dotnet issues in this group. ... earth it is so important to defend dotnet in a VB6 group is for me just hard ... not show up as replies to my Q, ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6 support on Vista
    ... Like I said...if it was specifically for VB6, ... about "information about how to extend your app through Visual Basic.NET" ... | ¤ Well, whether or not that is my plan is not the point. ... it the VB6 Resource Center is misleading. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... ¤ just add a new type if you need it. ... Yes but it ports as a Short so any assumptions are unaffected. ... copying code from Vb.net to Vb6 can not be denied. ... All of those with "also-ran" complexes are ...
    (microsoft.public.vb.general.discussion)