This is certainly a start. But, it seems to be focused on the ability to manage a single control. What I need is the ability to set properties on multiple controls by checking to see if a control or controls are currently "selected". I then display a grid where I can set the properties in question to those "selected" controls in one simple process vs. selecting each control and drilling through the property sheet one property at a time, then updating the table for that one change.

Our current FoxPro builder is much more efficient because we can set multiple properties and do a table update all at once.

Any Ideas?

bob


>See if anything in this link helps get you started:
>
>http://groups.google.com/group/microsoft.public.dotnet.languages.vb/browse_thread/thread/433b7a134012efc2/7c77b17f5f87825d%237c77b17f5f87825d
>
>
>>In FoxPro we created a builder that would allow us to select one or many objects on a form, and pop up a builder so we could set properties, and then build tables in FoxPro or SQL server based on the changes etc. we made to the custom properties of those objects (like tablename, fieldname, etc.)
>>
>>Anyway, here we are converting to .NET and C# and I was wondering if anyone has read a good article on how to customize Visual Studio to create a "Builder"? Can it even be done?
>>
>>Thanks!
>>
>>Bob