Yes, it's possible. However the following features are not yet implemented in the Silverlight version, so you might get unexpected results if you are using them: ContainerNodes, ShapeNode.RotationAngle, spanning cells in TableNodes.

Stoyan

Are you using controls hosted in DiagramNodeAdapters?

At this time the only thing you can do is derive from DiagramNode and use RegisterItemClass with some id that will be the same in both your WPF and Silverlight application. We'll think of some way to load hosted controls for the 1.0.3 release, perhaps some event that will let you resolve the class named saved in WPF to a corresponding Silverlight class.

You could derive from DiagramNodeAdapter in WPF and ControlNode in Silverlight and use RegisterItemClass to enable custom serialization of your types. The derived classes could simply set the internal Control to an instance of what's defined in your Xaml. Then override SaveToXml and LoadFromXml to save or load the properties of the hosted controls you are interested in. We'll probably be able to implement some builtin support for loading WPF files into DiagramLite in 2-3 weeks.

Just to make sure that I'm being clear on our design, the way that we create the DiagramNodeAdapter instances that become part of our drawings is solely through drag/drop. We drag an item out of a custom toolbar and then reconstitute our custom control (that is built from a XAML template) on the drop. When we add the custom UIElement to the diagram, the DiagramNodeAdapter gets created; and, of course, this cannot be resolved when we open it in DiagramLite.

I'm sorry if I'm being dense here, but I'm not sure how inheriting from DiagramNode or DiagramNodeAdapter on the Wpf side will help. I see that we need to have a DiagramNode instance saved in our Wpf diagram so that it can be reloaded in DiagramLite; but we can't seem to get the drag/drop from our toolbar to work when we do it this way.

Perhaps I need to send you a more complete example offline so that you can provide some additional guidance? Or perhaps you could post a code sample that demonstrates the Wpf-to-Silverlight compatibility?

We are approaching a deadline on our project and need to get the Silverlight side of things implemented as quickly as possible.

Still, creating a new type for each of your custom controls doesn't look like that good idea. We'll add some events to let you resolve the type of the hosted control in Silverlight. There is another difficulty; there is no XamlReader class available in Silverlight to read automatically the properties saved by XamlWriter in WPF, so we'll have to add SaveControl and LoadControl events in the WPF version similar to the ones in DiagramLite 1.0.2.

Hi,

Try this version:
https://mindfusion.eu/_beta/wpftosilverlight.zip

Now DiagramLite.dll should be able to load files saved by Diagramming.Wpf.dll when the diagram contains custom controls. You must handle the DeserializeControl event in Silverlight to load custom controls as shown below.

private void testLoadControlWpf()
{
	d.DeserializeControl += DeserializeControl;
	d.LoadFromXml("diagram.xml");
}

void DeserializeControl(object sender, ControlNodeEventArgs e)
{
	var elt = e.XmlElement.Elements().First();
	e.Node.Control = new TextBox { Text = elt.Value };
}
 

We haven't added SerializeControl and DeserializeControl events in the WPF version; it still saves hosted controls using XamlWriter. So you must check what XML elements are generated for your controls by XamlWriter and parse them accordingly on the Silverlight side. We could add SerializeControl and DeserializeControl events in WPF too if you prefer to implement serialization yourself in both WPF and Silverlight.

I hope that helps,
Stoyan