What's the state of play with “Visual Inheritance”

Question

We have an application that has to be flexible in how it displays it\'s main form to the user - depending on the user, the form should be slightly different, maybe an extra

Answer 1

I think I've found a way how to avoid this problem.

Don't hook the Form_Load Event in your parent form, this will break the designer.

Also don't take the Default empty constructor away from Visual Studio in the Parent Form. If you want to have Dependency Injection, create another constructor.

Like this:

public ProductDetail()
{
    InitializeComponent();
}

public ProductDetail(ISupplierController supplierController) : base()
{
    InitializeComponent();
    this.supplierController = supplierController;
}

You can then still do this from your inherited Form:

public NewProduct(ISupplierController supplierController)
    : base(supplierController)
{
    InitializeComponent();
}

This worked for me so far, and I had some weird designer issues too.

cheers, Daniel