Not to mention, if you share your code, using VFP like syntax could confuse the other programmers.

>Its a crutch for vfp programmers who want to learn .net. I realize its .net code but still, if you want to learn .net then learn .net. Don't rely on quasi-vfp-.net thingys...
>
>That's all I'm saying.
>
>>>I don't mean this in a bad way, but, if you want to use vfp, use vfp, if you want to use .net then use.net. Mixing the two is a bad idea in my mind.
>>>
>>
>>The VFPToolKit is .Net. It's a library of .Net methods taylored to the VFP developer but it is still .Net. I find if very useful not just because it helps me do things that I know how to do in VFP but also because it consolidates what would have been many lines of code into one line. It's really no different than many types of wrapper classes out there or ones that I've written myself. Often times I will refer to the help file to see the code used to implement certain methods but I see no reason not to use the VFPToolKit method in many of those cases.