Conversation
--- updated-dependencies: - dependency-name: LiveChartsCore.SkiaSharpView.WPF dependency-version: 2.0.0 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
the
dependencies
--- updated-dependencies: - dependency-name: LiveChartsCore.SkiaSharpView.WPF dependency-version: 2.0.0 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/nuget/MyMoney/LiveChartsCore.SkiaSharpView.WPF-2.0.0
branch
from
8076d60 to
6aab408
Compare
…PF-2.0.0' of https://github.com/jm6271/MyMoney into dependabot/nuget/MyMoney/LiveChartsCore.SkiaSharpView.WPF-2.0.0
…iaSharpView.WPF-2.0.0
jm6271
approved these changes
Apr 4, 2026
jm6271
deleted the
dependabot/nuget/MyMoney/LiveChartsCore.SkiaSharpView.WPF-2.0.0
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated LiveChartsCore.SkiaSharpView.WPF from 2.0.0-rc5.4 to 2.0.0.
Release notes
Sourced from LiveChartsCore.SkiaSharpView.WPF's releases.
2.0.0
It has been a long journey to build a charting library that works seamlessly across all .NET UI frameworks. Today, we’re excited to announce the first stable release of the library.
This release doesn’t introduce new features; instead, the focus has been entirely on stability. More than 150 new tests have been added to ensure the library remains reliable well into the future.
What’s next for the library?
There are many excellent charting libraries available, but LiveCharts was created to help developers build stunning, modern UIs. At the moment, there are no examples or showcases that truly demonstrate the library’s full potential—so that’s what’s coming next. Expect new examples that highlight what LiveCharts can really do.
What's Changed
New Contributors
Full Changelog: Live-Charts/LiveCharts2@v2.0.0-rc6...2.0.0
2.0.0-rc6
After months of deep work and iteration, this release is finally here. There is XAML and hot reload support, reworked rendering for serious performance gains, and leaned hard into source generation to clean up and future-proof the codebase. Oh, and yes: LiveCharts is now AOT-friendly. It’s faster, cleaner, and more flexible than ever.
Seamless XAML Integration via Source Generators
LiveCharts now uses a powerful source generator that automatically transforms chart objects into designer-friendly UI components. For example, the generic LineSeries now has a corresponding XamlLineSeries class—part of a new naming convention where all UI-bound types are prefixed with Xaml. These components support data bindings, themes, hot reload, and full design-time integration:
This update dramatically improves the chart design experience. You can now fully style your charts using pure XAML, including theme support—no more ViewModel hacks or SkiaSharp dependencies just to customize visuals. In previous versions, UI customization often required logic in the ViewModel, which led to tightly coupled and less maintainable code. That’s now a thing of the past.
Documentation for XAML platforms has been fully updated (thanks, Copilot!) to showcase the new syntax. While the new XAML-first approach is recommended, the legacy syntax remains supported for backward compatibility.
On non-XAML platforms, MVVM usage has been phased out from examples across the site and repo, reflecting a cleaner, more platform-native approach.
Rendering is significantly faster
The rendering pipeline has undergone a deep overhaul. LiveCharts now manages SkiaSharp resources far more efficiently, with cleaner, hardware-accelerated implementations and tight synchronization with the OS screen refresh rate. We've also added custom integrations for UI frameworks—most notably, full support for the Uno Skia renderer.
SkiaSharp shaders, paints, and text blobs are now cached wherever possible, resulting in dramatically faster rendering times, smoother animations, and reduced resource consumption across the board.
Previously, LiveCharts relied on a fixed render loop that invalidated the control every ~16ms to simulate a 60 FPS refresh rate. While functional, this approach forced redraws regardless of whether the system was ready to display them. Now, rendering is fully delegated to the OS or UI framework. For example:
This shift gives LiveCharts precise control over when and how frames are drawn—resulting in better performance and smoother visuals across platforms.
While it's hard to quantify the full performance gains (older versions lacked the benchmarking tools introduced in this release), the difference is substantial. Benchmarks in #1915 and #1936 offer a glimpse, but real-world usage shows even greater improvements.
As a bonus, there's now a "low-ish level" sample that removes the SkiaSharp dependency entirely—using Direct2D via Vortice—while still reusing 99% of the charting logic. This opens the door to even more rendering flexibility in the future.
Smarter Architecture with Source Generators
While this is an internal feature, it deserves the spotlight—because it radically simplifies how LiveCharts is built and maintained.
The library now uses a unified codebase, and a source generator automatically transforms core chart components into UI controls tailored for each supported framework. This means we write the logic once, and the generator handles the rest.
In previous versions, adding a new property to a chart control was a tedious, error-prone process. You had to manually define:
It was repetitive, fragile, and frankly exhausting.
Now? It’s magical. The generator takes care of all the boilerplate, translating properties and control logic across frameworks automatically. The result: a cleaner, more maintainable codebase—and a much more enjoyable development experience.
... (truncated)
Commits viewable in compare view.