>The CLR doesn't support it. It would require changes to the CLR to make it work.

You’re saying that the CLR does not support simple file IO operations? I beg to differ.

>Those changes won't happen...and if they were, all .Net languages would have access to it, again making VFP just like VB .Net.

You are right, Microsoft has already made that decision. Actually, I would love to see VB.NET, C#, etc. have the data processing capabilities of VFP.

>We are MUCH better off where we are.
Well, thats your viewpoint and you're entitled to it.


>
>
>>
>>I appreciate the feedback. I guess I missed the boat on all of the previous discussions dealing with these issues. The part I'm fuzzy on is why for example the VFP data engine could not be ported to managed code and run within the CLR. VFP's native data engine is file based and requires no more than simple file IO operations. The CLR's System.Data.IO provides this capability. I would have envisioned a set of CLR compliant runtime classes that provide VFP's functionality. From this viewpoint I don’t see why any functionality would have been lost.
>>
>>