>>Me, too. I think it's a neat bridge into .NET and nice way to share some of the Fox philosophy with other .NETters. And, no, I don't think it means that anybody has to stop using Fox *g*, but it's always fun to learn something new, too.
>
>
>Yes, I have the same line of thinking... I´m developing my VFPCOM MTDLLs to be used in .NET, and once I´m on VS.NET, it´s really cool to have a set of functions that we know and love. :)

Yes. Sometimes the most tedious part of working with .NET was knowing how to do something in VFP, but not knowing even what it might be called in .NET, or where to look in the help.

>and, that´s a lot less code for us on C# now. Thank God (and Kamal)! ;)

One thing we want to do is make sure that where it makes sense to use the native code, that's made clear. For example, some functions are really better handled directly in C# or VB.NET.