>>>>
>>>>I would like to know that MSFT is absoultely committed to keeping future versions of Windows compatible with today's VFP apps for the next 25 years or more.
>>>
>>>Microsoft is absolutely committed to it's stockholders. Microsoft is certainly not committed to the programming community in general, and to the VFP community in particular. Remember how they dumped VB5 for VB6 and VB6 for VB.NET?
>>>
>>>Our company recently finished a major .NET project. I think it will take .NET programming another decade to reach the levels of productivity Foxpro programmers take for granted.
>>>
>>>Theoretically, VS 2005 is an almost perfect product. Practically, I think it is clunky, buggy, resource intensive and manpower wasteful.
>>>
>>>Where there are no decisive technological reasons to move to .NET (e.g. multiple languages etc.) VFP gives much, much better value in most aspects of application development. The overpowering reason to move to .NET is because MS is forcing you to.
>>>
>>>Just my 2 cents. I would be happy to hear other peoples feeling on this.
>>I feel exactly the same.
>>
>>I develop with c# and with vfp9, and when i need the job done, i go for VFP.
>
>Hi Joaquim.
>
>Just out of curiosity... when do you go for C# then?
>
>Abraços.

Sorry Ivan,

I was out in vacation and missed your message.

About the question you asked: i started developing in c# about 2 years ago, and if i need net development i go for c#, but if i need developing for a PC or a group of PCs (and i usualy need) then i have to use VFP (it takes about 1/10 the time).

Cumprimentos,
Joaquim