var uxs = new SLaB.Utilities.Xaml.Serializer.UI.UiXamlSerializer();

string mystrXAML = uxs.Serialize(MyPanel);

but in my panel, I had a control that has a Polyline and other stuff. After Serialization, the Points in the Polyline were delete. but the good thing, I can serialize the Polyline alone, like:
string myPLXAML = uxs.Serialize(MyPanel.PLControl.polyline);
polyline is the name of Polyline, I try to create a public property like

public Polyline MyPolyline
{
get { return polyline; }
set { polyline=value; }
}
But doesn’t work… any idea????

Thanks for sharing your knowledge with us.
I am using your XamlSerializer.
I have run across the following problem.

I Create a rectangle in blend with a gradient fill.
I load it in silverlight using XamlReader.Load()
and it looks good. I then export it using your
UIXamlSerializer.Serialize().
It does not output the colors or the gradient stops.

Here is what i load into silverlight.

And here is what get exported using the uiserializer.

Any suggestions on what to try to get the colors and gradient stops exporting?

Thank you for you time.

Thanks for sharing your knowledge with us.
I am using your XamlSerializer.
I have run across the following problem.

I Create a rectangle in blend with a gradient fill.
I load it in silverlight using XamlReader.Load()
and it looks good. I then export it using your
UIXamlSerializer.Serialize().
It does not output the colors or the gradient stops.

Here is what i load into silverlight.

And here is what get exported using the uiserializer.

Any suggestions on what to try to get the colors and gradient stops exporting?

Thank you for you time.

One of the specific error messages I am getting from the parser says:
Cannot set unknown member ‘Microsoft.Expression.Shapes.RegularPolygon.Data’

May I ask a question: when, in Xaml, you use x:Name to create a class field and link to it a part of the UI, what form does that take when introspecting with the Reflection API? These appear to be internal fields, but I don’t see how to find them with the API … now I haven’t read all of your code, and it likely is there, but I wondered if you could assist …

Also … an observation … there appears to be a lot of frustration in the Silverlight Xaml community over behavior that was in one release, but is not now, having to do with Namescopes. CreateFromXaml was “here” in one release, and it was somewhat replaced with Application.LoadComponent and XamlReader.Load … but not quite, as these appear to keep information in an internal (or really hard to get at) location that ultimately seems to require x:Name should not be used. Your XamlSerializer (and a corresponding Deserializer) could provide a way around the problem, it seems, by providing a way to both use a Xaml to instantiate a new UI, and then subsequently hack around the Namescope problem by replacing the x:Name uses with placeholders that would permit linking of loaded components with FindName (using the replacement name).

Now my thought might be nothing short of silly, and you might have an alternative fix. pBut it seems that, especially if one could learn how to reflect on these internal fields in combination with your Serializer, a somewhat painful problem could be sidestepped until the Silverlight team put that functionality back.

Again, thanks for your work … very helpful to those of us who are, in comparison, significantly new to this space.

Well done on you implementation!