Re: What is the status of VB6 & DOT.NET ?




"---Pete---" <hthXXXX@xxxxxxxx> wrote in message
news:4400f4c4.88639875@xxxxxxxxxxxxxxxxxxx
On Sat, 25 Feb 2006 08:45:26 -0800, "Steve Gerrard"
<mynamehere@xxxxxxxxxxx> wrote:


Steve Gerrard,
Even though MS has released a 2005 version of Visual Studio,
it does not tell me what percentage of basic programmers are
using VB6 versus VB .NET . I'm just trying to get an idea of how
successful or unsuccessful MS was a getting people to switch
off of VB6 or.. if making the swich to .NET was a bad idea if MS
seems to be abandoning their marketing efforts for the product,
as someone recently told me was the case.


My first post was somewhat tongue-in-cheek, I guess I should have added a smiley
:}

I think a better question is - which software development system is MS
supporting and further developing? The answer to that is .Net. Then you can
instead ask how many people are abandoning MS development tools for other
products, platforms, and systems. The notion that MS would give up producing
their development system is silly.

How many are jumping ship? Depends on where they work, and who their target is.
Lots of web development is on other platforms. Despite efforts to dummy it down,
MS will have a tough time selling .Net based programming as a simple, carefree
system for beginners - it is just too elaborate for that to be realistic. I
think lots of companies have or will adopt it for serious in-house
server/intranet/special-purpose software, as well as for interfacing with ERP
systems and the like. As for commercial apps, I don't know, is there any money
in that anymore?

I see it as an addition to the toolbox -suitable for some things, not so much
for others. At work I have VB6, VS 2003, and VS 2005, all living happily
together, all for in-house development. The databasey-serverish apps go to .Net;
the techy engineering apps and quicky utilities go to VB6. That's my story, and
I'm sticking to it - for a while, anyway...


.



Relevant Pages

  • Re: Conversion Problem
    ... were creating web apps, or even apps for a mobile device, I surely wouldn't ... but for desktop apps I surely wouldn't want to use dotNet. ... VB6 sixes help sucks rocks. ... don't have to be a control array and they don't have to be the same type. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Alternatives
    ... These Apps don't deliver larger performance (there were ... those are hacks to work around the limitations in the ... problem in VB6 whilst using WinAPIs - I'm using the WinAPI ... How 'bout the console api? ...
    (microsoft.public.vb.general.discussion)
  • Re: Microsoft and trust
    ... DotNet certainly meets the criteria WE ALL ASKED FOR. ... your VB6 apps were pretty darn crude. ... were a little too slavish to the needs of the CLR but not to do so would ...
    (microsoft.public.vb.general.discussion)
  • Re: Are People Making Money in VB6?
    ... How many of you folks actually make a living today writing in VB6? ... retirees might enjoy fly-fishing or reading. ... I no longer bother to wonder whether my apps could earn me any money. ... boost to my little grey cells that programming brings. ...
    (microsoft.public.vb.general.discussion)
  • Re: Vista 64 and Visual Studio 6
    ... 64 and eventually Windows 7. ... Not sure exactly what to tell you other than I've been using VB6 on Vista 64 for quite some time now. ... that just means that your apps should "work" if run by a user with non-admin rights. ... MS had to support DOS apps for MANY years after DOS was declared dead. ...
    (microsoft.public.vb.general.discussion)