What time will v2 released on nuget? about livecharts2

[beto-rodriguez]

You can now install an early version from Nuget:

Avalonia:
https://www.nuget.org/packages/LiveChartsCore.SkiaSharpView.Avalonia

Winforms
https://www.nuget.org/packages/LiveChartsCore.SkiaSharpView.WinForms

WPF
https://www.nuget.org/packages/LiveChartsCore.SkiaSharpView.WPF

Xamarin
https://www.nuget.org/packages/LiveChartsCore.SkiaSharpView.XamarinForms

Docs should be ready soon, for now you can try to browse the samples folder in this repo.

[beto-rodriguez]

@ClubberLangG

there are core packages

https://www.nuget.org/packages/LiveChartsCore.SkiaSharpView/

https://www.nuget.org/packages/LiveChartsCore/

then any platform require these 2 packages.

[ClubberLangG]

Can you split the nuget and have a "Core" nuget, by example in your samples you have the "ViewModelSamples". It should be independent of WPF or WinForms etc...

Thanks

[jasonpp]

You can now install an early version from Nuget:

Avalonia: https://www.nuget.org/packages/LiveChartsCore.SkiaSharpView.Avalonia

Winforms https://www.nuget.org/packages/LiveChartsCore.SkiaSharpView.WinForms

WPF https://www.nuget.org/packages/LiveChartsCore.SkiaSharpView.WPF

Xamarin https://www.nuget.org/packages/LiveChartsCore.SkiaSharpView.XamarinForms

Docs should be ready soon, for now you can try to browse the samples folder in this repo.

Nice bro.

[langejay]

Are there any pages or documents floating around that help developers (C#/WPF) update from LC0 to LC2? I notice objects like ScatterPoint and SeriesCollection need replacing/changing. Would be nice if there was a cheat sheet for some of these changes.

TIA

(I am a Geared, paid user)

[CasperH2O]

Are there any pages or documents floating around that help developers (C#/WPF) update from LC0 to LC2? I notice objects like ScatterPoint and SeriesCollection need replacing/changing. Would be nice if there was a cheat sheet for some of these changes.

TIA

(I am a Geared, paid user)

Hey @langejay did you find anything related to this? We are also looking into migrating from v0 to v2 but when replacing the packages we had about 300+ errors to fix.