>>You have your opinion. What do you think he is trying to achieve; to big-up VFP or diminish .NET?
>
>I think neither. Just relating his experience.

But why though? If this was the other way round, the Foxers would be up in arms.

>>The main point is that 3 months to evaluate a technology like .NET is not doing himself or the technology any justice whatsoever.
>I agree that he didn't become as productive as he could of, but being an experienced developer, he could extrapolate from the 3 months.

You know that VFP development is very different to .NET - experienced in Fox, depending on what you have done can make you relatively un-qualified in the .NET world eg., Little or no exposure to XML, little or no exposure to SQL server, little or no exposure to dealing with disconnected data, little or no exposure to strong typing, little or no exposure to VS, little or no exposure to data middleware technolgies like ADO/ADO.Net.

From an OOP perspective, in many ways, VFP developers have an advantage in learning .NET but in all other respects, non-VFP developers (say VB6/Delphi devs) are coming from a better place because that are more used to the separation of the parts that these environments bring, unlike being in the one single Fox Box.

The OP could have been totally and utterly overwhelmed by .NET, dependent on his experience. Imagine having to start learning SQL server (or similar), .NET classes/namespaces, C# language, .NET OOP, ADO.Net, Winforms, WebForms, XML, VS - what a lot to take in in just three months ...