Re: VB6, VB2005, or Something Else?

Tech-Archive recommends: Fix windows errors by optimizing your registry

Paul,

No I'm sure Microsoft didn't have to do a lot things that broke code. Of
course that would have
placed some significant limitations on the product since adopting certain
architectures would have
conflicted with those in .NET, and probably would have taken another year
or two before it was
released. They didn't even get all the planned features back into the
initial version of Visual
Basic.NET. That's the reality you're ignoring.

Look, they could have brought out C# on schedule, all of the OO lovers would
have been over the moon. If they had told us that it would take a year or
two to bring out a version of VB that saved our code, I am sure we would
have all been happy.


They chose wisely. Any other choice would have saddled them with a second
class language for .NET.

No way. I am sure that we would have been happier to have a first class C#
and a second class VB and have been able to get our code accross the
barrier.

¤ How many different people must answer you before you *get a clue*? Check
the
¤ headers and look at our different posting histories - we are not the
same person
¤ posting with different personas, we are distinct individuals with
radically
¤ different histories and perspectives that somehow have come to a common
¤ conclusion - based on an apparently obvious truth. You may choose to
refuse to
¤ discern the truth, but even a blind man knows that the rocks at the
bottom of
¤ the cliff won't feel any better for having refused to acknowledge or
perceive
¤ them.

You speak much of truth. Woe is you in that it would appear to be your
bane.

You apparently don't get it Paul. If one of my clients says I got something
wrong. I take a look at it, but with a certain scepticism. I ask around and
try to get additional testimony. Maybe I got it wrong, but then maybe my
client has got it wrong. But if hundreds of my clients tell me in no
uncertain terms that I got it wrong, I think that it is quite obvious that I
got something wrong.

Gary


.

Relevant Pages

  • Re: VB6, VB2005, or Something Else?
    ... I tell my clients that that certain functionality is only used by ... ¤ If I had that attitude I wouldn't be in business for long. ... if just ONE of my clients demands that I put a certain functionality ... If there are issues with porting the GoSub code then perhaps ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... ¤>¤ after we had hundreds of thousands of lines of code in place already. ... The point should also be made that Microsoft didn't actually /have/ to break our ... I've already accepted the "truth", but it appears to be an obstacle you're unwilling or unable to ... You may choose to refuse to ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... ¤> No I'm sure Microsoft didn't have to do a lot things that broke code. ... That would have been a sure fire way to kill the language. ... But if hundreds of my clients tell me in no ... believe that Microsoft did the "right thing". ...
    (microsoft.public.vb.general.discussion)
  • Re: Distributing excel reference to client that doesnt have excel
    ... ¤ I am distributing an app that references Microsoft Excel Object ... My problem is some of the clients do not have Office installed. ... Can I have the client install the Office Primary Interop Assemblies ... The type libraries or interop libraries do not provide the actual ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6, VB2005, or Something Else?
    ... ¤> Actually I had already amended that number, not that two or even a hundred ... that my clients didn't like that I would still be ignoring them. ... you have to understand that the number of complaints concerning the removal of GoSub ... If there are issues with porting the GoSub code then perhaps someone would like to provide ...
    (microsoft.public.vb.general.discussion)