You may already know that I wrote BuilderB as a free public domain add-on for VFP, then I added it to VFP 6.0 with the new name of BuilderD (same basic source code). This is interesting feedback. I'm having lunch with a lead program manager on the VS 2005 shell/IDE team on Friday, and I plan to demo VFP 9.0 features and some extensibily features the XML editor in Whidbey. I will be sure to cover builders and BuilderB in the demos. I am interested in learning what the priorities should be for continued extensibility in VS, what tools should be created for VS add-ons, and what VFP features should be added to VS. Thanks for this feedback, send more anytime. :)

>BuilderD, BuilderB; heck, just give me aselobj() <s>
>
>The common thread through all the VFP user's comments about .NET is very simple: if I make the switch, I will lose my productivity, even after I learn the gazillion .NET classes.
>
>Application production is different than application creation, in the same way that being a chef is different than being a gourmet cook. Both may turn out the same product; but the chef does it about 5 to 10x the speed of the gourmet cook, and has to, in order to stay in business.
>
>Hank
>
>>>Hi Ken,
>>>
>>>I've read a few articles and papers on creating builders in .NET, and while it's doable, it's still a very big pain. I'd love to see a paper that created a framework for building builders that made it as easy as it is in VFP. Custom builders save us about 50% of the time required in designing forms, minimum.
>>
>>Sort of like a BuilderD for .Net. That would rock!