Re: VB.NET Discussion

Peter,

You asked a "put up or shut up" question. Karl put up an example. Now you
want to whine about it.

You know VB6 is going to break in upcomming releases. You know it's
doubtful they'll even try to patch it. Yet you're asking people whose
*mission critical* applications are at risk to put their heads in the sand.

While there is risk (as Karl pointed out) in MS breaking VB runtime the far
greater risk is with components. I personally don't know of a serious
application that does not depend on at least one third party component (a
lot more notes for you). Very few of those are still supported because the
vendors recognize that with MS abandoning the language they must go
elsewhere. Those will break first, and will break the applications.

> You've become a one-note band and I for one am tired of listening.

So, what are you doing here?

Dan

"Peter Aitken" <paitken@xxxxxxxxxxxxx> wrote in message
news:OiS98$hVFHA.2172@xxxxxxxxxxxxxxxxxxxxxxx
> "Karl E. Peterson" <karl@xxxxxxxx> wrote in message
> news:Oii6LfaVFHA.3432@xxxxxxxxxxxxxxxxxxxxxxx
>> Peter Aitken wrote:
>>> "Karl E. Peterson" <karl@xxxxxxxx> wrote...
>>>> Peter Aitken wrote:
>>>>> I'm not sure I agree with you. In theory what you say is true but I
>>>>> cannot imagine MS doing anything with the OS to "break" VB6 apps.
>>>>
>>>> The limits of your imagination are duly noted...
>>>>
>>>> http://support.microsoft.com/?kbid=321047
>>>
>>> Did you bother to read that article? It is a minor glitch in XP that
>>> was fixed with a service pack and there is no mention of VB. I can
>>> only assume you posted the wrong URL.
>>
>> LOL! You are _such_ a poseur. No assumptions, there! <g>
>>
>> Have you ever actually worked within Classic VB? Ever looked within the
>> Object
>> browser? Or at what references are made within *every* 32-bit Classic VB
>> application?
>>
>> That KB clearly shows that Microsoft not only can, but has, broken
>> deployed VB
>> applications by shipping new operating systems and/or patches. The trend
>> *will*
>> accelerate as they have now abandoned it from their regression suite.
>> --
>> Working Without a .NET?
>> http://classicvb.org/petition
>>
>
> Do you have the slightest idea how silly you sound? You claim that MS is
> breaking VB applications and the best you can do is a KB article that
> tells us that (1) There was a minor problem with one function that did not
> "break" anything, (2) That at worst caused some occasional and minor
> rounding errors, and (3) Was fixed. Is it April 1st again or what? Calling
> me names does not advance your argument and in fact is a pretty sure sign
> of the weakness of your position. If there are problems with VB6 apps
> breaking then I want to know about them, but quite frankly you don't seem
> to know what you are talking about. It seems to me that you (and others)
> have some weird obsession going on with knocking MS and .Net. You've made
> a few good points but on close examination your position seems to be so
> much hot air because you cannot back it up with anything but hand-waving.
> You've become a one-note band and I for one am tired of listening.
>
>
> --
> Peter Aitken
>
> Remove the crap from my email address before using.
>


.

Relevant Pages

  • Re: VB6 -vs -vb2005
    ... complete overkill for the applications I wish to write. ... then you have to go back and maintain a VB6 application. ... too many prototypes became production ... When you NEEDED to ignore the data type of a variable, ...
    (microsoft.public.dotnet.general)
  • Re: VB6 - VB.NET post SP6
    ... I'm curious about how others feel the likely changeover trend from VB6 to ... VB.NET applications is likely to turn out over the next 2-3 years? ... early .NET betas. ... It was a bigish learning curve but I stuck with it until I was fairly ...
    (microsoft.public.vb.general.discussion)
  • Re: VB.NET 2008 not backward compatable?
    ... Did you ever compare a VB6 exe with a Net exe, in past downloading an VB6 applications took hours (for common people not for those who are so comfortable as you to work on every place with mega gigabytes connections. ... there are differences in the CLR which prevent execution of .NET 2.0+-based assemblies on the .NET 1.* CLR.) ...
    (microsoft.public.dotnet.languages.vb)
  • Class Help
    ... I have been tasked to upgrade a project from VB6 to VB.NET, ... Public with a Publi Sub New does not share across other applications. ... when ApplicationA runs it sets up some of the properties in DLLA, ... Microsoft has removed the GlobalMultiUse property ...
    (microsoft.public.dotnet.languages.vb)
  • Class Help
    ... I have been tasked to upgrade a project from VB6 to VB.NET, ... Public with a Publi Sub New does not share across other applications. ... when ApplicationA runs it sets up some of the properties in DLLA, ... Microsoft has removed the GlobalMultiUse property ...
    (microsoft.public.dotnet.general)