WPF Chart Library Platform Support Comparison

Most WPF charting libraries support exactly one framework: WPF. Some add WinForms. None of the four competitors covers C++ MFC, Delphi VCL, or ActiveX. ProEssentials is architecturally different — it is a native Win32 DLL charting engine with two complete API layers: a hierarchical .NET property interface for WPF and WinForms, and a standard C/C++ DLL API for MFC, Delphi, ActiveX, and any language with foreign function interface (FFI) capability. Both APIs access the same rendering engine, the same GPU compute shaders, and the same 1,000+ properties.

This matters because real organizations don't run a single framework. A defense contractor may have MFC-based data acquisition software, a WPF operator dashboard, and a Delphi legacy reporting tool — all needing the same charting capability. ProEssentials covers all three from one license, one set of documentation, and one support team. This page compares platform coverage, deployment characteristics, and the five chart objects available across all platforms.

Platform Support Matrix

The table below compares framework support across all five WPF charting libraries. SciChart supports only WPF (plus separate iOS/Android/web products not applicable here). LightningChart supports WPF and WinForms. Syncfusion and DevExpress support WPF and WinForms with DevExpress additionally offering Delphi VCL and ActiveX in separate product lines. Only ProEssentials covers all eight platform targets from a single product.

ProEssentials covers 8 out of 8 platform targets. DevExpress covers 5 (across separate product lines). LightningChart and Syncfusion cover 3 each. SciChart covers only 2 — WPF and C++/CLI. For organizations that need C++ MFC, Delphi, ActiveX, or cross-language DLL access, ProEssentials is the only charting library in this comparison that provides native support.

Two API Layers, One Engine

ProEssentials exposes its entire feature set through two interchangeable API layers that access the same underlying native Win32 DLL. The .NET property interface provides IntelliSense-rich access through hierarchical property objects (Pesgo1.PeData.Subsets = 5). The C/C++ DLL API provides direct access through PEnset/PEvset function calls (PEnset(hObject, PEP_nSUBSETS, 5)). Both APIs set the same internal state in the same native DLL — there is no performance difference, no feature gap, and no behavioral divergence.

This dual-layer design means a .NET developer can access the native DLL handle via PeSpecial.HObject for advanced scenarios, and a C++ developer can create chart windows using standard Win32 PEcreate() calls. A C++/CLI mixed-mode application can use either API — or both — in the same project. The rendering engine, GPU compute shaders, export functions, printing, and all 1,000+ chart properties are identical regardless of which API layer is used.

Every property, every enum value, every chart type works identically across both APIs. The .NET enum ManualScaleControl.MinMax maps to the C++ constant PEMSC_MINMAX. The .NET event PeDataHotSpot maps to the Win32 message CYCHART_DATAHOTSPOT. Documentation covers both — the C++ DLL constant names are listed alongside every .NET property path.

Platform Deep Dives

ProEssentials provides dedicated controls for each platform — not wrappers, not interop shims, but native implementations that use the platform's own control hosting model. Here's what each platform gets:

WPF (.NET)

ProEssentials provides dedicated WPF controls (PegoWpf, PesgoWpf, Pe3doWpf, PepsoWpf, PepcoWpf) that integrate directly into XAML layouts. These are not WinForms-in-WPF interop wrappers — they are proper WPF FrameworkElements that support WPF layout, data binding, and the WPF rendering pipeline. The controls use Direct2D and Direct3D rendering engines natively, with full GPU compute shader support for large datasets.

All five chart objects are available as WPF controls. NuGet installation adds the controls to the Visual Studio toolbox. The hierarchical .NET property interface provides full IntelliSense. Over 40 included WPF example projects demonstrate every chart type, real-time streaming, annotations, contour charts, 3-D surfaces, and interactive dashboards.

WinForms (.NET)

ProEssentials WinForms controls (PegoWin, PesgoWin, Pe3doWin, PepsoWin, PepcoWin) are standard System.Windows.Forms.Control descendants that drop into any WinForms designer layout. They use the same native DLL and the same .NET property interface as the WPF controls — same code patterns, same property names, same rendering engine.

SciChart does not offer WinForms controls. LightningChart provides WinForms controls. Syncfusion and DevExpress both offer WinForms charting. However, none of the competitors share a single native engine across WPF and WinForms the way ProEssentials does — with competitors, WPF and WinForms chart controls are separate codebases with different APIs and sometimes different capabilities.

C++ MFC / Win32

ProEssentials provides a native C/C++ DLL API (Pegrpapi.h) with over 100 functions for chart creation, property access, data loading, export, and printing. Chart windows are created with PEcreate() and configured with PEnset()/PEvset() function calls using PEP_ property constants. This is not COM interop or .NET hosting — it is a standard Win32 DLL that links directly into any C/C++ application.

The DLL API covers the complete ProEssentials feature set: all five chart objects, GPU compute shaders via Direct3D, real-time streaming, annotations, export to PNG/JPEG/SVG/EMF, printing, and interactive zoom/pan. MFC integration is straightforward — create the chart as a child window of any CWnd/CDialog, configure properties via PEnset/PEvset calls, and handle Win32 messages for events.

No other charting library in this comparison offers a native C/C++ DLL API. SciChart, LightningChart, Syncfusion, and DevExpress are .NET-only — C++ applications would need to host the CLR, create a managed wrapper, or use COM interop. ProEssentials is the only option for pure native C++ charting on Windows.

Delphi VCL and ActiveX / COM

Delphi developers access ProEssentials through the same native DLL API used by C++ MFC. The Pegrpapi.h header translates directly to Delphi unit imports. Chart windows are created with PEcreate() and configured with the same PEnset/PEvset pattern. All five chart objects, GPU rendering, and the complete property set are available.

ActiveX/COM access is provided through registered OCX controls. VB6, Classic ASP, and any COM-capable environment can host ProEssentials charts. The OCX controls expose the same property set as the DLL API and .NET interfaces — same rendering engine, same behavior, same output.

DevExpress offers a separate Delphi VCL product line and ActiveX controls, but these are different products from their .NET charting with different APIs and different capabilities. ProEssentials uses the same engine across all platforms — what works in WPF works identically in Delphi, MFC, and ActiveX.

Legacy Migration and Long-Term Investment Protection

ProEssentials has been in continuous development since 1993 — over 30 years of backward compatibility. Applications written for ProEssentials v4 (MFC, circa 2000) can be recompiled against v10 with minimal code changes. The property constant names (PEP_nSUBSETS, PEP_faYDATA, etc.) have remained stable across every major version. New features are added as new properties — existing properties are never removed or renamed.

This matters for organizations with long-lived codebases. A defense program that started with MFC in 2005, migrated its UI to WPF in 2015, and plans a modernization in 2030 can use ProEssentials throughout — same licensing, same support, same charting engine adapting to each platform transition. The C++ DLL code from the MFC era still compiles. The WPF code from 2015 still runs. The investment is preserved.

Competitors that launched in 2012–2015 (SciChart, LightningChart) have no equivalent track record. Syncfusion and DevExpress have long histories but their charting components have been rewritten multiple times across different platform generations, often with breaking API changes between major versions.

The Bottom Line on Platform Coverage

ProEssentials is the only charting library that covers WPF, WinForms, C++ MFC, Delphi VCL, and ActiveX from a single native engine. Two interchangeable API layers (.NET property interface and C/C++ DLL API) access the same rendering engine, the same GPU compute shaders, and the same 1,000+ properties. Deployment is 5–8 MB with no activation, no account, and no external runtimes. All five chart objects work identically across every platform.

SciChart supports WPF only. LightningChart supports WPF and WinForms but requires online activation. Syncfusion and DevExpress support WPF and WinForms with different codebases per platform. DevExpress additionally offers Delphi and ActiveX but as separate products with different APIs. For organizations that need cross-platform Windows charting — especially those with C++ MFC, Delphi, or air-gapped deployment requirements — ProEssentials is the only option that covers every target from one product, one license, and one support relationship.

Performance & Architecture

How GPU compute shaders and on-demand rendering deliver speed without continuous power draw.

Pricing & Support

Perpetual licensing, free unlimited support, and 5-year TCO compared across all five libraries.

3-D Scientific Charts

Surface, contour, waterfall, 4-D, Delaunay — GPU compute shader rendering with production code walkthrough.