Text 6318, 143 rader
Skriven 2005-07-24 21:55:00 av Robert Comer (1:379/45)
   Kommentar till text 6314 av Ellen K. (1:379/45)
Ärende: Re: MS Antispyware uses VB6 runtime?
============================================
From: "Robert Comer" <bobcomer@mindspring.com>

> There are way too many applications out there written in VB6 for them to
> make it impossible to run VB6 apps,

All I can say is they made a dreadful decision in not having a clear upgrade
path, it's the first development tools/language vendor I've ever known to do
that, and there's probably more VB6 coders out there right now than any other
language.

It just doesn't make business sense to trust that VB6 stuff will keep running.

>heck, it's still possible to run DOS
> apps.

Our parent company is having serious problems keeping their DOS clipper app
running on XP, memory issues that weren't there before...

>And .Net has "COM Interop".

That doesn't help upgrading VB6 code all that much. (That help in calling old
COM components from vb.net)

- Bob Comer


"Ellen K." <72322.1016@compuserve.com> wrote in message
news:7oe8e15569eq6ortjohk7aaenqkmb6dg6g@4ax.com...
> There are way too many applications out there written in VB6 for them to
> make it impossible to run VB6 apps, heck, it's still possible to run DOS
> apps.  And .Net has "COM Interop".
>
> On Sun, 24 Jul 2005 16:12:30 -0400, "Robert Comer"
> <bobcomer@mindspring.com> wrote in message <42e3f4f7$1@w3.nls.net>:
>
>>> I'm not saying use the upgrade wizard rather than rewrite, I'm saying
>>> leave it in VB6.
>>
>>As I've said before, there's no guarantee the VB6 development environment
>>will continue to function *now*, much less in the future. (sure, you can
>>get
>>paid for support if it breaks, but it's not cheap)  And as anyone knows
>>with
>>corporate environments, you need to be able to fix this as business rules
>>change, or there are bugs discovered.  And past longhorn, there's no
>>guarantee the VB6 runtime will function ever. (and only a nebulous
>>guarantee
>>it'll be supported in longhorn)
>>
>>To sum it up, it's to high a risk *not* to rewrite it.
>>
>>- Bob Comer
>>
>>
>>
>>
>>"Ellen K." <72322.1016@compuserve.com> wrote in message
>>news:urs7e11kqsqbusrpem0uom8osd2vm0nqgb@4ax.com...
>>> I'm not saying use the upgrade wizard rather than rewrite, I'm saying
>>> leave it in VB6.
>>>
>>> On Sun, 24 Jul 2005 09:02:08 -0400, "Robert Comer"
>>> <bobcomer@mindspring.com> wrote in message <42e3901a@w3.nls.net>:
>>>
>>>>>I don't think you have to rewrite your old stuff.
>>>>
>>>>If you want it to run well you do.  The changes between VB6 and VB.NET
>>>>is
>>>>massive.  Running it through the VB.NET upgrade wizard does not get you
>>>>a
>>>>working program if the program is any more advanced than a "Hello world"
>>>>type.  Sure, given a lot of time you can fix the differences, but that
>>>>same
>>>>amount of time can most likely be taken to do a rewrite using all the
>>>>new
>>>>stuff (or a different language altogether.)
>>>>
>>>>- Bob Comer
>>>>
>>>>
>>>>"Ellen K." <72322.1016@compuserve.com> wrote in message
>>>>news:din6e1hna3158pa89es1380tal3lkvt7bd@4ax.com...
>>>>>I don't think you have to rewrite your old stuff.
>>>>>
>>>>> On Sat, 23 Jul 2005 06:54:36 -0400, "Robert Comer"
>>>>> <bobcomer@mindspring.com> wrote in message <42e22095$1@w3.nls.net>:
>>>>>
>>>>>>> If the spyware product they acquired was not based on VB.NET, how
>>>>>>> can
>>>>>>> they
>>>>>>> be asking why MS is not using VB.NET? Did they expect MS to rewrite
>>>>>>> it?
>>>>>>
>>>>>>Actually yes, everyone should expect them to rewrite it, after all,
>>>>>>Microsoft told all those millions of VB6 developers out there that
>>>>>>they
>>>>>>had
>>>>>>to rewrite their apps by deadending VB6 like they did.
>>>>>>
>>>>>>>Did VB.NET even exist when the product development began?
>>>>>>
>>>>>>It didn't exist when all our VB5/VB6 code was written, but so what,
>>>>>>that
>>>>>>doesn't mean that I don't have to rewrite everything to insure it
>>>>>>keeps
>>>>>>working in the future.
>>>>>>
>>>>>>- Bob Comer
>>>>>>
>>>>>>
>>>>>>"Gregg N" <invalid@invalid.invalid> wrote in message
>>>>>>news:42e1bdf1$1@w3.nls.net...
>>>>>>> Rich Gauszka wrote:
>>>>>>>
>>>>>>>>Microsoft acquired Giant, the company that produced the Spyware
>>>>>>>>detection
>>>>>>>>program, in December 2004, and lost no time in making it available
>>>>>>>>to
>>>>>>>>users the following month.
>>>>>>>>
>>>>>>>>"This whole issue begs the question," writes our reader, "why is
>>>>>>>>Microsoft
>>>>>>>>using an unsupported development environment against their own
>>>>>>>>guidelines?
>>>>>>>>Just another case of' 'Do what I say, not what I do'...
>>>>>>>>
>>>>>>> If the spyware product they acquired was not based on VB.NET, how
>>>>>>> can
>>>>>>> they
>>>>>>> be asking why MS is not using VB.NET? Did they expect MS to rewrite
>>>>>>> it?
>>>>>>> Did VB.NET even exist when the product development began?
>>>>>>>
>>>>>>> Gregg
>>>>>>
>>>>>
>>>>
>>>
>>
>

--- BBBS/NT v4.01 Flag-5
 * Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)