>Hello all.
>I'm looking for that thread which discussed the technical reason why VFP couldn't/could be a part of the .NET studio.
>
>Can any one give me the thread ID. I promise I'm NOT trying to rehash an old arguement. I just wanted to understand what the concept was.
>
>Thanks.

Well, I guess this is not the answer you are looking for, but here goes anyway: <g>

I believe that the real reason was that MS was not willing and/or able to put the nescessary resources into developing a VFP.NET. The official reason was, IIRC, that VFP would loose its strengths, like native cursor engine, dynamic command evaluation etc. In my opinion, this is BS, and the recent development of IronPython shows at least that dynamic languages indeed can be written to run under .NET. In fact, IronPython runs faster on .NET than the traditional C implementation does(!).


Eyvind.