That's exactly what I was thinking.... it would be hard to pick a subset of .net functionality.

>IMO, we should be able to instantiate any class. Why should it be limited to a few?
>
>>
>>I didn't mention it in a letter, but to individuals at conferences asking about .NET usage with VFP. We have a prototype of a utility allowing VFP to call .NET Framework classes without having to subclass or create COM objects from the .NET Framework classes. We are not ready to discuss or release any further details, it is just an experiment, and what I am asking from VFP developers is for them to tell me what .NET Framework classes they would want to be able to instantiate and use (and why) from within VFP without having to subclass and COM wrap them first.