"Cor Ligthert [MVP]" <no************ @planet.nl> wrote in message
news:OG******** ******@TK2MSFTN GP11.phx.gbl...
Ken,
Just as I thought <sigh>... Posting suggestions for dotNet from an
"Actual VB6 developer" is like talking into a vacuum. HUGE waste of time
because the direction dotNet's taking has already been set in stone so,
as a VB6 developer, our "suggestion s" are nothing more than something for
the dotNet product team to print out and use as toilet tissue.
I disagree this completely with you. In my opinion is there now to much in
VB.Net what would not be there if there was not that big VB6 advocacy,
which seems for me extremely stronger than the Linux one.
At least I am not very lucky with some of the so called improvements in
version 2005 which becomes because of this advocacy, which have helped to
improve VBNet with the at least not always logical behaviour of VB6,
without that they knew anything from VB.Net.
Every developer knows in advance what it the result of these kind of
improvements. However the VB6 avocacy is strong.
Just my opinion.
Cor
Well... I can't count the number of times I've seen an MS employee say "post
your ideas" and, when we do, they're completely ignored. The problem with
most of the "improvemen ts" as far as VB6 migration goes, since VB6 has
always been "just a toy" to MS and no one there used it for any reasonable
amount of time, they're implementing features they "assume" VB6 developers
want (can't seem to provide a decent immediate window or single procedure
view though).
So, what you're saying is, B# is getting worse as a result of these
"improvemen ts" eh? That doesn't surprise me at all. VB6 compatibility isn't
just some band-aid you can simply paste on top of a framework to please VB6
developers. Personally, I have 10s of thousands of lines of code that are
instantly broken by dotNet. Since most of my projects include several
classes that perform the exact same thing, no matter what project they're
in, I thought it would be a good idea to feed those through the "wizard" and
never have to deal with them again. If that "wizard" found one of those
"pre-converted" classes, it could simply swap one file for another, instead
of parsing the class and reporting tons of errors every single freaking time
it comes across one of these exact same classes in a project.
Since B# is a completely new language, it should never have been called "VB"
in the first place. If only they'd have been honest, we wouldn't be having
these issues today, at all. VB6 support in B# could've been completely
dropped.
NET Software Legend Juval Lowy agrees with that too, saying the only thing
VB6 has in common with VB.Net is the letters "V" and "B" in their names. You
can hear that in the following podcast....
VB6 Glass Ceiling
http://blogs.duncanmackenzie.net/dun...0/28/3148.aspx
--
Ken Halter - MS-MVP-VB (visiting from VB6 world) -
http://www.vbsight.com
Please keep all discussions in the groups..