John,

>The toolkit is beneficial to everybody. Unfortunately, calling it the "VFP" Toolkit might make some give short shrift to the idea.

I suppose so if folks are predisposed against VFP.

>I would have called it something like "The Developer Extension" Toolkit. I probably would have taken Ken Matson's suggestion of renaming things from strtofile to StringToFile, etc. None of this diminishes the usefulness of the toolkit.

Ok..

>
>As for specific developers, I would say ANY developer coming to .NET should get use out of it...

Now, I haven't had the time to really look at the toolkit but isit written in .NET (VB.NET?) or is it a VFP COM/DLL?




>
>
>
>>John,
>>
>>>I think the VFP toolbox is both a proof of concept and an aid to those Fox developers who wish to migrate to .NET. It should also be of help to non-Fox developers going to .NET.
>>
>>?? As in VB programmers for example? That makes sense I suppose - as long as they can duplicate what the VFP toolkit does in VB I suppose. What about other programmers also seeing the power of VFP and then investigating it as well?
>>
>>IOW, doesn't the door swing both ways here?
>>
>>
>>
>>
>>>
>>>My adivice is to look at the toolkit, not for what it is, but for the idea it represents. i.e., don't scoff at the toolbox for the way it is out of the box. Rather, use it, customize it and in the tradition of Fox, make it your own by tailoring it to your needs...
>>>
>>>
>>>
>>>>EXACTLY! And If I don't like the parameters or the order, then I can change that - and if I want to change or enhance functionality - then I can do that - and if I don't need all the functions - then I can take some out - and if I need some others then I can add them - and - wow - I'm not using the "VFP toolbox" anymore! ;-)