Wpf: Alternative to xaml.cs file containing only deafult constructor and InitializeComponent() call

Question

I use MVVM. Is there any convenient way not to have xaml.cs files but somehow still calling InitializeComponent()?

Answer 1

Hi Naeron,

Check this out:

<Window x:Class="WpfApplication1.TestBrowser"
        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        Title="Initialize Component Test"
        Height="300"
        Width="300">
    <StackPanel>
        <ListBox x:Name="lb"/>
        <x:Code>
            <![CDATA[
public TestBrowser()
{
  InitializeComponent();
  lb.ItemsSource = new[] { "Hey" };
}
]]>
        </x:Code>
    </StackPanel>
</Window>

When such a XAML file is compiled, the contents inside the x:Code element get plopped inside the partial class in the .g.cs file.

I still would not recommend this practice. As for me it makes code less readable, and I'm not sure whether Blend or Kaxaml understands it.