Porting System.Windows.Forms.DataVisualization to .NET core

[dreddy-work]

Porting System.Windows.Forms.DataVisualization to .NET core

[danmoseley]

This assembly eagerly attempts to load OleDB types - which is problematic unless and until we port OleDB to .NET Core. However it looks quite possible to segregate the OleDB types so that they are only loaded if the caller actually wants to use OleDB and this would be worth doing.

All the usage is in a single class ChartImage and it is all protected by checks like if (obj is OleDbDataAdapter). Those can likely be replaced with if (obj.GetType().FullName == "System.Data.OleDbDataAdapter") or similar -- and only if the test is true then would it call into a new class that would reference these types properly and cause them to load.

[weltkante]

@davidnmbond apparently this is already mostly done, @merriemcgaw commented something along those lines in #510

[danielabbatt]

I work on a project which generates charts server side into images and it would be great to get that onto Core as it's the only part of the app which still relies on .NET Framework.

[davidnmbond]

Would love to see this - there is no reasonable way to achieve charting in .NET Core without it!
Is there a way I can do the required work?

[kirsan31]

We have DataVisualization in preview 4 now. And most of sad thing it's considered deprecated :((
I posted a question about it...

[zsd4yr]

I have added guidance on using the new ported types to our porting guidelines https://github.com/dotnet/winforms/blob/master/Documentation/porting-guidelines.md#include-the-systemwindowsformsdatavisualization-pack

[danineuss]

@zsd4yr
I am currently trying to port my application to .NET Core 3.x and have stumbled upon the not supported (...).DataVisualization.Charting library. Is this fixed today? The URL that you posted on April 19 '19 leads into 404 land ..

Thanks already 🙏🏽

[weltkante]

You want to check the document in the release/3.0 branch. Its usable for initial porting but generally charting is not supported going forward to newer .NET versions, so you may run into bugs eventually when WinForms changes and this library wasn't updated. You can keep using it if you create your own build and maintain it yourself I assume, or switch to a different library with full external support.

[RussKie]

The library is no longer officially supported.
The docs link: https://github.com/dotnet/winforms/blob/main/docs/porting-guidelines.md#include-the-systemwindowsformsdatavisualization-pack
Here's a package that should help you to migrate to .NET, but it won't work in the new designer: https://www.nuget.org/packages/System.Windows.Forms.DataVisualization.

[danineuss]

Thanks Igor for your reply! I am having issues installing the nuget package but in essence this is all I would need to do in order to make my repo ready for moving it to .NET Core?

On August 13, 2021, radioman85 ***@***.***> wrote: The library is no longer supported.  The docs link: <https://github.com/dotnet/winforms/blob/main/docs/porting- guidelines.md#include-the-systemwindowsformsdatavisualization-pack> Here's a package that should help you to migrate to .NET, but it won't in the new designer: <https://www.nuget.org/packages/System.Windows.Forms.DataVisualization>.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub <#112 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe- auth/ADUA746WAXA33DS3566WQDLT4SB5JANCNFSM4GHSYDTA>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification- email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification- email>.