Visual Studio designer woes, with the collection designer and an abstract class
-
I'm writing a Component for some of our Windows Forms applications. This component has a collection property exposed, and the collection is of a simple type with two members; one is a Control reference, the other is a reference to an abstract base class type. Now, in the designer, I want the developer to be able to choose from the available classes that derive from that abstract base class, and I would like the selected class's instance to have all its properties visible in the designer (as an expandable object.) Does anyone with Component/designer experience have any ideas for me?
-
I'm writing a Component for some of our Windows Forms applications. This component has a collection property exposed, and the collection is of a simple type with two members; one is a Control reference, the other is a reference to an abstract base class type. Now, in the designer, I want the developer to be able to choose from the available classes that derive from that abstract base class, and I would like the selected class's instance to have all its properties visible in the designer (as an expandable object.) Does anyone with Component/designer experience have any ideas for me?
Adam Maras wrote:
Does anyone with Component/designer experience have any ideas for me?
There are several good MSDN articles introducing adding Designer support to your custom controls This one might be a good place to start[^] With each platform version there are some changes but much of the basics are the same or at least similar. My experiences are through VS2005 so .NET 2
led mike