Re: Visual Basic Express 2008 Edition and KB278379 by Ken
Ken
Mon Oct 13 17:30:28 CDT 2008
"Mr. JYC" <MrJYC@discussions.microsoft.com> wrote in message
news:8E833398-A322-4D17-AF86-84E3ACA09FE9@microsoft.com...
>> dotNet questions *and* answers belong in dotNet groups. VB6 questions
>> *and*
>> answers belong in VB Classic groups. "How do I fix my plumbing" questions
>> *and* answers belong in a home improvement group. Pretty simple, really.
>
> Except when you don't know what tools to apply. I am an MCSE, MSCA, and
> my
> experience is in servers, networks, and databases. While do know some
> Visual
> Basic (mostly Access), C, C++, and Java, I don't know the difference
> between
> VB6, VB Classic, and .NET. It would really be helpful is someone could
> send
> me a link that discusses the differences from a high level perspective.
>
> Never assume anybody knows as much as you do and also never underestimate
> anyone!
The very first response to your question gave names of the proper
newsgroups.
The *core of the problem* is, dotNet's "VB" isn't compatible with the
original.
We do VB1 thru 6 here... we were hoping for 7 and on, but MS marketting just
decided to tack the name "VB" onto their new product, hoping we'd all "jump
for joy" at the thought of completely abandoning and/or rewriting our entire
codebase for no good reason at all.
They've had over 10 years to come up with "something" to match VB6's truly
RAD environment and haven't been able to. They're still teaching VB6 in
classes throughout the US, so even the schools aren't ready to toss their
existing work in the trash.
Mixing the two languages in a single group does nothing but make it harder
for "newbies" to find answers. VB6 and dotNet q/a's mix about as well as oil
and water. It's *not* our fault.
VB6 is VB Classic... VB.Net is "the new coke" (which is where the "Classic"
name comes from). VB classic compiles to native machine code. VB.Net
compiles to an intermediate language which requires extra steps (and money)
if you don't like people looking at your source code... which is why *quite*
a few component vendors simply jacked up their prices and supply the source
along with the component... so, the developer is paying *extra* for
something very few developers want or need... just another case of the
honest people paying higher prices because of dishonest people.
If you're new to these groups, it may seem like we picked your question and
started a flame war.... that's not the case. That "MVP" who helped (I
assume, I don't see his posts, or try not to) *knows* where dotNet q/a's
belong, yet he answers them here, *knowing* darn well that he's been asked
not to *tens*, if not *hundreds* of times.
If you peek back in a few days, you'll see the same thing repeated over and
over and over... it's not limited to the "Classic" groups, though... Try
asking a "Classic" q/a in a dotNet group... after being called every name in
the book, someone /may/ provide the name of the correct group.... and, if
you own flame-proof underwear, try asking a "Classic" q/a in a C++ group.
btw... too bad you don't have a copy of VB6 around... since VBA and VB6 are
very close, the code you wrote for Access would port *a lot* easier to VB6
than it will to dotNet.
--
Ken Halter
Part time groupie