Breaking Changes in SciChart WPF SDK v9

Although there are some breaking changes in the SciChart WPF v9 SDK (vs version 8.x), we are hoping that for most customers SciChart WPF v9 is a drop-in replacement.

In the majority of cases, SciChart WPF v9 should be a drop-in replacement for customers of SciChart WPF v8, with a very high proportion of backward compatible APIs. A list of breaking changes that we know about are found below. If you find more and require assistance, please Contact Us and our team will be happy to help.

What Backward Compatibility Testing have we done?

At SciChart we make an SDK consumed by thousands of developers worldwide, and don’t have access to all of your code. We do however, have access to our own WPF Examples, Sandbox, Tutorials and Test-Cases. To that end, we have analyzed backward compatibility by using the SciChart WPF SDK v9 in SciChart WPF v8 Sandbox Examples and Tutorials.

Platform Changes

Dropped target framework: .NET Core 3.1 (netcoreapp3.1) is no longer supported. .NET Core 3.1 reached end-of-life in December 2022. SciChart v9 targets .NET Framework 4.6.2 and .NET 6.0 (and later). If your application targets earlier .NET versions, you will need to retarget to .NET 6.0 or later before upgrading to SciChart v9.
Removed package: The SciChart.Drawing.DirectX NuGet package has been removed. The DirectX renderer was superseded by the VisualXccelerator renderer in SciChart v6 and is no longer maintained. If your application references SciChart.Drawing.DirectX, remove the package reference and use VisualXcceleratorRenderSurface instead. There shouldn't be any additional code changes required beyond removing the package reference and switching the render surface type.

Breaking Changes in SciChart 2D API

Obsolete method: SciChartSurface.UnsubscribeInnerSeriesBaseCollections() has been made Obsolete. This method was previously public but performed almost no useful work when called externally. It will be removed in a future release.
Obsolete method: BaseDrawingProvider.GetVertexArray<TVertex>(int expectedCount, ref TVertex[] currentArray) static method has been made Obsolete. This is an internal utility that was previously part of the public API.
Obsolete classes and methods: deprecated legacy axis synchronization API - AxesSynchronizationManager, AxisSynchronizationHelper, and AxisBaseViewModel.AddToSync() / RemoveAxisFromSync() are now obsolete. They have been replaced by the new MVVM Axis Synchronization API with IAxisViewModel.RangeSyncGroupId for linking VisibleRange across charts and IRangeSyncTransform for range conversion
API change: The following types have been made internal: VxPen, VxSolidColorBrush, and VxRenderSetting.Resolve(). These are internal implementation details of the VisualXccelerator renderer that were previously public. If your code references these types, please contact support for guidance on alternatives.
Renamed class: PointMarkerTemplateToPropertyConverter has been renamed, fixing a typo in the original class name. If your code or XAML references the old name, update it to the corrected spelling.
Behavior change: The default tooltip labels for OHLC and Candlestick charts have been changed from “Highest” and “Lowest” to “High” and “Low”, aligning with standard industry terminology.

Breaking Changes in SciChart 3D API

API change: SceneEntityCollection has been made internal. This class was part of the public API but is intended to be used internally by SciChart3DSurface to manage scene entities. If your code directly instantiated or subclassed SceneEntityCollection, use the SciChart3DSurface.SceneEntities collection property instead.

Consultancy Services Available

As a paid customer of SciChart WPF if you are within your support subscription, then you will get access to SciChart WPF v9 for free.

What your support subscription covers is:

Access to (ability to develop applications with all major/minor versions of SciChart)
Bug fixes, updates
Technical support ‘how do I do X’ questions as well as assistance on best-practice implementing the software.
Best practice advice on getting the best performance out of SciChart.

What we don’t include is:

Custom work such as new features or enhancements or workarounds to the chart.
Performance analysis of your applications to improve application speed with SciChart (or wider performance analysis)
Upgrading your applications to the latest versions when you have lots of customisation.

For these ‘not included’ aspects of technical support, our consultants are available to help you on a one-to-one basis, coding or advising over MS Teams/Zoom/Web conference and assisting you to upgrade to the latest version, and performance profile or tune your applications to be the best they can be.

If you require these services, then get in contact with sales, and we can provide a quote for hourly work.