Re: vb or vfp: advice needed
From: Dan Freeman (spam_at_microsoft.com)
Date: 06/07/04
- Next message: sp: "Run-time DLLs for Europa"
- Previous message: Sietse Wijnker: "Re: DLL?"
- In reply to: Chip Orange: "Re: vb or vfp: advice needed"
- Next in thread: John Spiegel: "Re: vb or vfp: advice needed"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 7 Jun 2004 14:37:56 -0700
Chip Orange wrote:
> "Dan Freeman" <spam@microsoft.com> wrote in message
> news:OfZTU4lSEHA.1172@TK2MSFTNGP11.phx.gbl...
>> Chip Orange wrote:
>>> No doubt, a rewrite is in order.
>>>
>>> I need reasons why it's better to do it in vfp rather than vb.net.
>>
>> It may not be "better" either way. <g> The thing is, there is no
>> absolutely right answer here. Just tradeoffs.
>>
>> Dan
>>
>>
>
> Dan, obviously you're right; I'm trying to find out even what the
> tradeoffs are??? If you could point me at a few that would help.
>
> thanks.
>
> Chip
Read Ed Yourdon's book "Death March". (Reccommended reading even if you
weren't facing this type of decision. <s>)
Bringing in consultants who insist on bringing in a new technology (solely
for the sake of bringing in the new technology) is almost always a guarantee
for project failure.
If you have in-house Fox knowledge, much of it will convey to any work done
in VFP. Virtually none of it will convey to a foreign technology.
Many years ago, when I was working with Robert Green (former VFP guru, now a
product manager on the Visual Studio team), I remember his first project
done in VB. Every few hours he'd show up at my desk absolutely RANTING about
this function or that command being missing with no alternative. Robert
probaly doesn't remember those little "conversations" but I'll never forget
them. <g>
Dan
- Next message: sp: "Run-time DLLs for Europa"
- Previous message: Sietse Wijnker: "Re: DLL?"
- In reply to: Chip Orange: "Re: vb or vfp: advice needed"
- Next in thread: John Spiegel: "Re: vb or vfp: advice needed"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
