Tech Off Thread

2 posts

XamlObjectWriter fails with bindings?

Back to Forum: Tech Off
  • User profile image

    Hi All.

    I'm Trying to load the following basic xaml with XamlObjectWriter (.Net 4)

            Title="MainWindow" Height="350" Width="525" x:Name="mainWindow">
            <TextBox Name="myTextBox" Height="23" HorizontalAlignment="Left" Margin="271,71,0,0" VerticalAlignment="Top" Width="120" />
            <Button Content="{Binding ElementName=myTextBox, Path=Text}" Width="100" Margin="97,4,306,0"/>



     The code is quite simple:

                XmlReader xr = XmlReader.Create("../../XAMLSimpl.xaml");

                XamlXmlReader reader = new XamlXmlReader(xr);

                XamlObjectWriter writer = new XamlObjectWriter(reader.SchemaContext);

                while (reader.Read())

                object res = writer.Result;

     When I run the the code I get the following exception (because the binding)

    {"A 'Binding' cannot be set on the 'Content' property of type 'Button'. A 'Binding' can only be set on a DependencyProperty of a DependencyObject."}

    A 'Binding' cannot be set on the 'Content' property of type 'Button'. A 'Binding' can only be set on a DependencyProperty of a DependencyObject.


    Which looks. If I try to use the old style code:

    FileStream reader = new FileStream("../../XAMLSimpl.xaml", FileMode.Open);
    object res = System.Windows.Markup.XamlReader.Load(reader);

     Everything works fine.

    Any suggestion?


    Many thanks in advance,







  • User profile image
    Rob Relyea

    see for some details.

    It depends what you are trying to do with your XamlNode loop...

    You could use the Wpf SchemaContext + your code (pass it to the constructor of the XamlXmlReader), and you'll get pass this binding problem.  But there are other things in XamlReader.Load() that won't happen. See the blog post for the list.

    Rob Relyea, WPF Team |

Comments closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.