>>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.