Im just trying to get a handle on where code that does work should be written in a Winforms application.

For example, in my sample Winforms application below, I have to binddata from a table in a database to a tree, and I do all that dataBinding etc in a BindTree() method. So do i call the BindTree() method after the InitializeComponent() in the forms constructor, or do i call the method in the Load event of the form?

Is there a best practice solution? Is there an advantage of one vs. the other?

Thanks

---

You are so wise...like a miniature budha covered in fur. -Anchorman

You should always favor the constructor. Code in the Load event is generally less efficient. By the time it runs, the window has been created. And updating properties now requires updating the internal control data as well as the window. ListView.Items.Add() for example is *much* slower.

Exceptions are a problem too in the Load event, there is no good way to let the caller know that initializing the form failed.

There is one case where you should use Load. Only then do you know the real Location and Size of the form. Which might be different from the programmed value because of StartPosition and automatic rescaling. Any code that lays out your form (say, positioning controls) should go in Load.

---

Hans Passant.

Both will work.

Check this link it will help

http://www.informit.com/articles/article.aspx?p=101720&seqNum=3

---

Thanks, A.m.a.L .Net Goodies
Remember to click "mark as answered" when you get a correct reply to your question

You should always favor the constructor. Code in the Load event is generally less efficient. By the time it runs, the window has been created. And updating properties now requires updating the internal control data as well as the window. ListView.Items.Add() for example is *much* slower.

Exceptions are a problem too in the Load event, there is no good way to let the caller know that initializing the form failed.

There is one case where you should use Load. Only then do you know the real Location and Size of the form. Which might be different from the programmed value because of StartPosition and automatic rescaling. Any code that lays out your form (say, positioning controls) should go in Load.

---

Hans Passant.

I did see a big difference in populating my treeview in the onload vs. the constructor, but i just wasnt sure what the 'correct' method was. directly writing code in the constructor didnt look 'right' i guess.

i will call my methods from the constructor and remove the load event.

thanks noBugz.

---

You are so wise...like a miniature budha covered in fur. -Anchorman