The long awaited .NET Core 3.0 from Microsoft is getting closer to release.The next major version of .NET Core, .NET Core 3.0, has recently entered Preview stage. It will include support for building desktop apps using Windows Presentation Foundation (WPF), Windows Forms (WinForms), Entity Framework (EF), Blazor, C# 8, and .NET Standard 2.1 (see First Look at .NET Core 3.0: C# 8, WPF, WinForms).
For a getting-started guide to .NET Core 3.0, please see Brian Lagunas’ post here.
In preparation for this, we’ve done some work to ensure that SciChart’s popular WPF Chart is compatible with the upcoming framework and that we can deploy dotnetcore compatible libraries to our users.
SciChart WPF for .NET Core 3.0 now available on Github
If you are a SciChart WPF Source-code customer, you can now access our .NET Core 3.0 Preview directly from Github. To get access (if you haven’t already), you can follow the steps at our page Github Repository for Source-Code Customers.
The two repositories: SciChartWPF (accessible only to customers of SciChart WPF 2D Enterprise) and SciChartWPF3D (for customers of SciChart WPF SDK Enterprise) now have new solutions which are compatible with Visual Studio 2019 and dotnetcore 3.0 Preview. Open these solutions & build to get a .NET Core 3.0 ready version of SciChart!
NuGet Packages for non-source-code customers coming soon
We intend to publish NuGet Packages of the compiled DLLs for regular customers of SciChart without source-code access soon. We have to change our licensing component because the one we’ve used since 2013 is not compatible with .NET Core 3.0. This may involve a breaking change (new type of license mechanism required), however, fundamentally the chart API will be the same, and will be a drop in replacement for SciChart WPF v5.x in the .NET Framework.
Once we have done this, we will announce on our Releases page and customers will be informed by our email newsletter.
Give us your feedback!
If you are a SciChart Source-code customer, and interested in using our WPF Charts in .NET Core 3.0, then please try out the solution on Github, and give us your feedback!