Well from my point of view it's a resources problem the reason why Microsoft is no porting VFP to .Net
why?
Simple Visual FoxPro ('cause Microsoft Fault) is not used so much now, you can see it in the jobs market, it's like 100 to 1 realtionship. Even at microsoft, .Net team it's much bigger than VFP (and it's amazing the work VFP team have made with less resources than the others teams). The VFP sales are no making much money to Microsoft. I'm sure that for SEDNA they have less resources to produce the product. It's simple no fair, because all this problems came from the poor marketing made to VFP since the First version. In DOS times a lot of applications were written in Fox we had a big piece of the market. But they have killed in a slow way the product at the eyes of neew developers. I'm sure that VFP is alive, thanks to the VFP team efforts and the comunnity.

Luis Navas



>I looked up an article yet which Einar's gave us link in UT. There is written a Cobol.NET version even. I know a lot of talked about this issue but I can't understand it. Why even a Cobol.NET possible and VFP.NET impossible. Ken said some reasons and I accept them (I reveal now because I'm not an expert in deep on technical and English issues) but I cannot understand anymore...
>
>http://www.ftponline.com/weblogger/forum.aspx?ID=6&DATE=06/07/2005&blog=#386