is call to InitializeComponent necessary in partial window class in code behind file?

Question

I ask because if you create a new WPF project in VS 2008 the default generated code is:

public partial class Window1 : Window
{
    public Window1()
    {
        InitializeComponent();
    }
}

However, commenting out the call to InitializeComponent does not prevent the application running.

Why is this?

score 1 · Answer 1 · edited May 23 '17 at 10:33

1

While the window will load up, you won't be able to use events or access the XAML from the code behind if you don't call InitializeCmponent.

Here is a good explanation

edited May 23 '17 at 10:33

Community

1
1

answered Oct 15 '10 at 21:54

mdm20

4,475
2
22
24

score 0 · Answer 2 · answered Oct 16 '10 at 15:49

Just right click the InitializeComponent call, then go to definition.

You'll see that the definition of InitializeComponent is just an XAML parser. Vital to load your WPF window and everycomponent in it. You can compare it with converting an XSD document to a CS or VB Class. Not necessary but pretty useful.

is call to InitializeComponent necessary in partial window class in code behind file?

2 Answers2