Where to put Constructor Code?

[Keith Smith]

Does it make more sense to put additional constructor code WITHIN the
InitializeComponent(); method? Or should I put it right after the
InitializeComponent(); is called (in the public Form1() method)?

 

[Olle de Zwart]

Does it make more sense to put additional constructor code WITHIN the
InitializeComponent(); method? Or should I put it right after the
InitializeComponent(); is called (in the public Form1() method)?

Well the InitializeComponent method is where the designer generated code
is placed. Although you can certainly add/change it if you want, if
there is no need to I would keep my own code out of there. You can place
your own constructor code before or after the call as long as you
realize that the designer generated code has to be executed before your
gui elements are initialized. So you would probably end up with
something like:

public Form1() {
//Ctor code that needs to be run before anything else
//InitializeComponent()
//Ctor code that needs to work with gui objects
}

 

[Patrick]

Does it make more sense to put additional constructor code WITHIN the
InitializeComponent(); method? Or should I put it right after the
InitializeComponent(); is called (in the public Form1() method)?

public MyClass():System.Windows.Forms.Form.Form
{
public MyClass()
{
InitializeComponent();
initializeSomeMore();
}

// ...

initializeSomeMore();
{
// more initializing
}

private void MyClass_Load(object sender, System.EventArgs e)
{
// more initializing
}
}

 

[Peter Jausovec]

Hi Keith,

I don't think you should put the code in InitializeComponent() method since
it is generated by desinger. Instead you could put your after/before the
InitializeComponent() call in ctor.