Adding a custom property designer to a form that will be inherited

Adding a custom property designer to a form that will be inherited

• AngelaL

  Rather than changing the designer for a form, you could add a StateMachineNode component to your form, which would sit in your component tray (or somewhere on your form, if you want some run-time user interface to it).  Add a smart tag to the component, and launch your designer form from a smart tag method.
  
  See the custom smart tag entry in Beta 2 help: ms-help://MS.MSDNQTR.v80.en/MS.MSDN.v80/MS.VisualStudio.v80.en/dv_fxdeveloping/html/42cc4a0c-9ab3-47e1-93b8-03b6a6ccf233.htm

  
  

• mahdi mansoori

  If you are only talking about adding custom properties then you don't have to have a custom designer to show those.
  
  If you still want a custom designer, then yes is it possible, but the problem is that the designer for a Form is internal to System.Design.dll, so your can't inherit from it.
  
  So you will need to reproduce any functionately that its provides (which will be huge job).
  
  What exactly are you trying to achieve
  
  

• BillM

  I am creating a state machine, that will enable or disable the controls on the form based on an enumeration member, all of our forms will be derived from this one.  Basically I want to create a dialog designer for the form that will have a list of all the states in the enumeration and a list of all the controls on the form at design time.
  
  Thanks!
  Kurt
  
• Adding a custom property designer to a form that will be inherited