Re: VB6, VB2005, or Something Else?


"Paul Clement" <UseAdddressAtEndofMessage@xxxxxxxxxxxxxx> wrote in message
news:oon942t13i9a4f5gn5mqjuanmlluk9505q@xxxxxxxxxx
On Tue, 18 Apr 2006 08:40:59 +0100, "Gary Nelson" <gn@xxxxxxxxxx> wrote:

Gary,

¤
¤ > ¤ Do...Loop is superior to While...Wend. What's the point?
¤ > ¤
¤ >
¤ > How is it superior? You want to replace While...Wend with Do...Loop.
Tell
¤ > me what the benefit of
¤ > doing that would be.
¤
¤ Since Microsoft has taken it upon themselves to clean up VB, why not
remove
¤ something redundant like While...Wend? Personally I have no problem with
it.
¤ To me it's fine that they left it in. Kind of funny that they changed
Wend
¤ to End While, but it doesn't bother me in particular as I generally use
¤ Do...Loop anyway. By the way, I at times copy and past code back and
forth
¤ between VB6 & VB.Net and these little details are always getting in the
way.
¤

I think you ducked the question. ;-)

Nothing can really be done about pasting VB.NET code to VB 6.0. A lesser
version of the product will
never support the newer features. Besides, it's never a good a idea to
copy code from a newer
version to an older version since there is simply no guarantee that it
will work as expected.

¤ > Bad analogy. No one said the problem was "in your head". But it
appears to
¤ > me that you're dismissing
¤ > potential solutions. You want an easy solution to the problem but
there
¤ > isn't one and never will be
¤ > one.
¤
¤ I don't know about you, but if I have a client that complains 'a little'
¤ about something he doesn't like in my program, I might pay attention,
and
¤ then again, I might not. If he complains 'A LOT' he has a lot better of
a
¤ chance of getting listened to.
¤

I'm sure you might listen. You may even be able to resolve it without
affecting other customers.

¤ >
¤ > ¤ As to Microsoft, I think where they went wrong was to consider VB6
¤ > ¤ programmers like novice users. The problem is that we are
programmers.
¤ > Some
¤ > ¤ of us have been programming longer than many on the .Net team. We
have a
¤ > ¤ very good idea of what can and can't be done. We know when we have
been
¤ > ¤ shafted. The problem is that now we are stuck between a rock and a
hard
¤ > ¤ place. We will be complaining for a long time to come.
¤ >
¤ > The product has moved on. Complaining may make you feel better but the
¤ > bottom line is that sooner or
¤ > later you're going to have to start considering alternative solutions.
¤
¤ I'll continue complaining as long as it hurts.

Fair enough.


Paul
~~~~
Microsoft MVP (Visual Basic)

" Nothing can really be done about pasting VB.NET code to VB 6.0."

Duh!

"A lesser version of the product will never support the newer features."

Define lesser, then list the necessary features that absolutely couldn't
have been constructed using additional keywords or 'blocked' segments (a la
the following runs in managed code) with VB6 as the root.

You won't come up with any.

Anything you do suggest will only be a reflection of how it should look like
C# or something - not a reflection of what would have been necessary to run
in a manged environment.

-ralph



.

Relevant Pages

  • Re: VB6, VB2005, or Something Else?
    ... By the way, the preformance of Gosub in PCode was quite good, it ... ¤ ... I'm not complaining about the necessary changes, ... that Microsoft intentionally and unnecessarily made it more difficult. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... Since Microsoft has taken it upon themselves to clean up VB, ... ¤ As to Microsoft, I think where they went wrong was to consider VB6 ... The problem is that we are programmers. ... We will be complaining for a long time to come. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... ¤> doing that would be. ... Since Microsoft has taken it upon themselves to clean up VB, ... We will be complaining for a long time to come. ... Microsoft MVP ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... ¤> ¤ Andre, ... ¤> ¤ The core problem with VB.Net is that the language itself is changed. ... GoSub is the only one of those you mentioned that was part of the core ... Not sure how you can say the majority of serious programmers used GoSub. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... ¤> ¤ Perhaps because it was considered uncouth to use gosub. ... ¤> ¤ programmers had the same opinion of VB. ... GoSub is about one step above GoTo so I could see why it would ...
    (microsoft.public.vb.general.discussion)
Loading