Hi Mike,

We (VFP developers) all know that MS wants to kill the fox. I'm surprised by your reaction because I was sure that by now you'd be exclusively working with .net. By that I mean for your new projects.

We (VFP developers) are probably seen like a bunch of maniacs by MS. They probably consider that the patient is in a profound coma only kept alive with some machines. But we (VFP developers) still try to convince them to keep the patient alive while they only want to disconnect the remaining machines. By the way machines that are left on their own hoping that they will stop functioning by themselves (for example marketing, developers department: Last I heard of they were 2 or 3 persons working on development of the product).

But again we (VFP developers also known as the maniacs) insist on trying new treatment to revive the patient but we're told that the patient is doing ok and there's hope but they don't want us to tell anyone else. It's just like they contacted all the members of the family just in case the patient would'nt make it through the night but they told us to keep it to ourselves. They told us "Don't bring someone that does'nt already know the patient".

Sure some members of the family still have hope for the patient and they still shout at MS to try new things to keep it alive but more and more of the members lost hope and left the place thinking that it's too late and they don't want to suffer no more knowing that whatever they suggest nothing will be considered. So eventually MS will be able to disconnect the machines because nobody will be there to try to stop them.

During those battles many members met a new friend. He's in great shape. He's even on top of many magazines. In his circles he's the star. So now because of meeting that new friend everything is getting so nice again. They know that this new friend won't be there forever but everyone says that he's the one to know so if everybody says that it must be true.

So the wheels turn...



>>>If VFP will always be a win32 app and Microsoft is moving to a new API, we need to start learning the development tools that will best exploit this new API (ie. Visual Studios .NET)
>>>
>>
>>Indeed. I wonder why so many can't see the logic of this.
>
>The logic is quite simple:
>
>1. Promote .NET as the successor to the Windows API.
>2. Then release an Operating System with its own API that expands on the .NET Framework locking developers to that new Operating System.
>
>Not that I'm complaining, but how many times has Microsoft said "Ok, we'll change" and then go on with business as usual?
>
>In any case, as far as what "harm" Ken has done those are your words. I'm not harmed in any way and don't see my comments as complaints as Ken has labeled them. Only exclamation. I'm surprised that the person in charge of marketing a product is resistent to using the product's name in his signature.