Re: Newbie Advice/Critiscism


"Rick Rothstein (MVP - VB)" <rickNOSPAMnews@xxxxxxxxxxxxxxxxx> wrote in
message news:eM$gB9ttHHA.768@xxxxxxxxxxxxxxxxxxxxxxx
the dotnet framework does have a lot of good things built in; it's just
a
shame that they never put a fraction of the effort into providing
similar
COM-based components for VB or actually creating a dotnet version
of the classic VB language.

If I remember correctly from a couple/few years ago, Karl once posted a
message somewhere based on an inside "source" that Microsoft had actually
moved a classic version of VB7 quite far along, but killed it in favor of
bringing out VB.NET by itself.

Karl... am I remembering this correctly?

Rick


This is specifically addressed to Karl, but I will horn in anyway. Your
question really depends on what you mean by "... quite far along".

[It has to be appreciated just how big MS is. Puzzling things out even if
you are an 'insider' takes on the aspects of the proverbial bind men and the
elephant. This is essentially what I know about it - probably just a tail
and a leg. <g>]

There had been an internal battle over VB ('96?). This battle was between
the Office Development Team and the Language group. The language group won
and at the time this was considered by VB developers a victory for the
language. There were high hopes the new features (constructors, namespace,
implementation inherentance, true libraries, etc) would be forth coming.
There were papers and some 'demos' showing these features. But strangly MS
started phasing out VB when VB6 was released. Many projects were turned over
to consulting firms. VB Programmers were being cut out. (Move to .Net or
exit) In most cases it was not a choice. Like an idiot it didn't strike me
as odd at the time. I thought it was just political fall-out over the
internal fighting. The 'newer' VB.Net teams were populated by very few "VB
people".

In 2000? there were a variety of general showings for selected authors,
editors, Fortune 500, developers, etc. During the multiple shows, the
virtues of dotNet was shown along with a short presentation of how "VB"
would be moved into the environment and of the obstacles in migrating it.

It was hard to tell if this Alternative was an actual product or just a
mock-up or even where it came from. I got to see some docs, but most of it
was oral in side-bar meetings. The impression was given that this was how VB
would look (the VB7). It was kludgy - similar to C's managed/unmanged. I
didn't mind that much, as it was after all, Beta 0.9. It think this is where
the idea of a "VB7/.Net" came from. But Karl can likely offer more
information.

Also one has to realize that MS like most companies actually start on the
'next' version long before the current one is out the door. "VB6" was slated
to have more features than were actually delivered. In looking back, IMHO
VB6 was a "drop what you are doing and ship" release.

Many of the participants later wrote glowing articles that when faced with
the choice they "talked MS" into abandoning any ties to the past and boldly
go forth into the future, blah, blah. While many may actually believe they
made that decision on their own, it is extremely obvious that the whole
thing was a well-orchestrated Charade. (Hindsight is 20-20.) It is also
interesting to note, that we all left with a bag of dotNet beta disks and
docs - but nothing was available for "VB7".

During the same period I attempted to contact many of my 'contacts'. They
were either gone, couldn't talk, or were re-assigned. The VB 'team' was
gone. The VB.Net team were charged with delivering a VB# language for the
CLI - period. So it is absolutely certain in my mind that neither they or
anyone near them - actually came up with a "VB7/Net". If such an item
actually ever existed, it has to have been a dying gasp of some VB remnant
group.

And just so no one thinks I am trying to place myself as some kind of
know-it-all. At the time I bought into the idea hook, line, and sinker. It
didn't seem that important, because MS was known for being backward
compatible, and there were still promises for more features for VB6.

They are keeping the lid on, but there is no doubt in my mind that the whole
story will eventually get out.

-ralph


.