Hi Cathi,

are you ducking on aselobj() <s> or did you just miss it?

Hank

>Hi Hank,
>
>Thank you for your feedback about the Toolkit. As far as your question about the help file referencing existing functionality in .NET, we are recommending using the .NET implimentation instead of using the Toolkit class. These recommendations are for the functions that are implimented in .NET very easily and there is no reason to call the Toolkit function instead. The help is to show how you would call the .NET language's version. You can use the Toolkit function instead though if you prefer.
>
>If you have anymore recommendations, please let us know on this thread.
>
>Thanks.
>
>>Hi Cathi,
>>
>>I found the helpfile confusing when it says (as it often does):
>>
>>This method maps directly to existing functionality in the .NET. Use the code listed in the Implementation section of the help detail instead.
>>
>>Does that mean "you can just as easily use the built-in functionality of .NET but use this if you want" or does it mean "you really shouldn't use this function, but should use the built-in .NET functionality instead"?
>>
>>Regarding functionality: wrapping controls so they can be bound directly to data (as WebMatrix does with XML and the grid control) would be nice to have, at least for quick and dirty testing.
>>
>>Wrapping the classes that handle builder functionality would be really nice: boy, what I'd give for aselobj()! (Give me that and I'll drive over to DevCon and celebrate over dinner with you <s>.)
>>
>>thanks for all the work you've put into this product, and into promoting .net here.
>>
>>Hank
>>
>>>3. What other information would be useful to include in the help file?
>>>
>>>The Visual FoxPro Toolkit for .NET team