Re: VB6, VB2005, or Something Else?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Paul,

¤ > There is even a KB article that dates back almost
¤ > nine years which recommends using alternatives.
¤
¤ Cite?
¤

Ken posted it.

It would have been nice if they had been a little more clearer about what
they were thinking.

¤ I'm not complaining about the necessary changes, I'm complaining about
the
¤ unnecessary ones.
¤

Well no, not unless you're changing the subject on me. You were referring
to the ability to copy and
paste code from the newer version to the older version.

Perhaps I'm not making myself clear. Let me give you a simple example.

Split is not available in earlier versions of VBA (for EXCEL), or VB for
that matter. If, for some reason I want to copy some code to an older
version I have to take that into consideration, and I have a function with
that funcionality for that purpose. I have no complaint about that. My
complaint is about all the little things that were 'adjusted' to make it all
the more difficult, and which provide nothing new and no advantages.

¤ Until now it wasn't necessary. The problem is that now they have cut off
a
¤ forward path for our VB6 code, so now it has become necessary to
innovate.
¤

Once again, I thought you were referring to a backward path, copying and
pasting code from the newer
version to the older version.

I was. I have never felt the necessity of copying code from VB6 to VB5 or
VB4. But now that we have to do dual development it has become a necessity.


¤ > Well in that case there should be a suitable replacement.
¤
¤ There is, it's called C#.
¤

According to whom?

¤ >If Microsoft recommends I use something
¤ > different several years prior to it's demise, as they did for GoSub,
then
¤ > I think that's fair.
¤
¤ Could you give us some insight as to how clear Microsoft's recomendation
¤ was? I am sure that stronger things have been said in favor of C# and
¤ against VB.
¤

Could you be a bit more specific? If Microsoft is now recommending C#
instead of Visual Basic I
would like a cite.

As clear as the recomendation not to use GoSub? Sure, as I mentioned before
at TechEd nearly all the demos are done with C#. To me that is as clear as
the piece you mentioned in KB.

They announced it (at the time) for the next version of Visual Basic,
which was .NET. I just stated
that.

What else needs to be clarified?

You consider that KB article to be an announcement? I thinking you are
stretching things a bit.


¤ In a letter to the editor of a recent edition of VSM (Vol. 16, No. 3)
it
¤ was stated: "I believe you should try to move to C# and drop Visual
Basic
¤ altogether."
¤
¤ That is not the first time that I have read similar statements...

I think you misspelled "opinions". Everybody has one.

"Opinions" on GoSub got it Killed.

Gary


.

Relevant Pages

  • Re: VB6, VB2005, or Something Else?
    ... ¤> language and it can be easily ... But if you're using several GoSubs in a Sub or Function then it's ... The ability to write bad code is not an excuse to use GoSub. ... I'd have to use a knife, but I would miss the screwdriver. ...
    (microsoft.public.vb.general.discussion)
  • 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?
    ... ¤> ¤ vFred. ... ¤> No one was really complaining about the removal of GoSub other than ... probably DOS BASIC apps and not Visual Basic apps. ... as they had never worked with a BASIC language before and had little or no ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... ¤ Couldn't the same be said of those who don't use GoSub? ... Since GoSub is part of the language ... Generally code posted in the forums are short secuences to solve certain ... Just like C programmers looked down upon VB programmers. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... ¤> Replacing GoSub code is trivial. ... have spaghetti code then hopefully you understand how it got that way to begin with. ... ¤> converting their GoSub code to equivalent Visual Basic.NET code. ...
    (microsoft.public.vb.general.discussion)