>>Hmmm... I see what you want. That would be alot of work. All of the forms would have to be converted, all the data handling code converted to ADO.Net... then there is the issue that VFP is not strongly typed, that would be a heck of a hill to climb. You would be forced to declare all your variables, that's for sure.
>
>not just declare the variables, but also declare their types, and stick to it, meaning, you can't change the type of a variable like we can in VFP. Same goes for method parameters and return. LOTS of lines of code would have to be rewritten...

Hi Claudio. Dont mix application porting with the ability to use VFP style commands and functions which are mapped to framework classes. Converting existing apps would be, I think, virtually impossible if for no other reason than strong typing. But being able to use VFP command/function syntax with a local data engine would be very nice for a VFP programmer even if they did have to start strong typing their variables. The truth is that several other languages are being ported. I dont think this is a technical issue as such but rather a financial one. I'm not an expert though so its only a 2 cent opinion :)