What additional capabilities does yFiles WPF have over yFiles.NET?
Questions & AnswersSummary
This article was written for an older version. It is only online as a reference for customers using this old version. The information it contains is probably out of date.
The latest information can be found in the yFiles documentation
Description
yFiles WPF uses WPF instead of WinForms, obviously. No more forms controls, but WPF controls, with styling, templating, easy animation, command binding, etc.
A very important feature of yFiles WPF is the addition of native WPF controls as nodes, labels, and even ports and edge segments, so your nodes can contain a complete WPF UI (buttons, textfields, movies, 3D content, hardware accelerated shader effects, etc.). Also, native XPS export has been added (but EMF export has been removed).
yFiles WPF contains a revised GraphML architecture and improved APIs that make better use of extension methods, generics, type-safety, lambda-expressions, etc.
The layout API has been transformed to conform to .NET coding standards which means no more y.@base.Graph, but yWorks.yFiles.Algorithms.Graph. Also, no more get/set like properties and byte constants, but .NET properties and enums in the layout API and no more Java compatibility classes for the collections, but .NET System.Collections.