Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
XPlot relies on things that are not .NET Standard
See original GitHub issueLooks like XPlot.GoogleCharts can only be .NET Standard if Google.DataTable.Net.Wrapper is also update to be .NET Standard
C:\GitHub\dsyme\XPlot\src\XPlot.GoogleCharts\XPlot.GoogleCharts.fsproj : warning NU1701: Package ‘Google.DataTable.Net.Wrapper 3.1.2’ was restored using ‘.NETFramework,Version=v4.6.1’ instead of the project target framework ‘.NETStandard,Version=v2.0’. This package may not be fully compatible with your project. [C:\GitHub\dsyme\XPlot\XPlot.sln]
Also GoogleCharts.Deedle --> Deedle, but I don’t mind about that one so much since I want to get rid of it, and there is a .NET Standard Deedle being prepared in any case
C:\GitHub\dsyme\XPlot\src\XPlot.GoogleCharts.Deedle\XPlot.GoogleCharts.Deedle.fsproj : warning NU1701: Package 'Deedle 1.2.5' was restored using '.NETFramework,Version=v4.6.1' instead of the project target framework '.NETStandard,Version=v2.0'. This package may not be fully compatible with your project. [C:\GitHub\dsyme\XPlot\XPlot.sln]
9 Warning(s)
Issue Analytics
- State:
- Created 5 years ago
- Comments:13 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@jackfoxy That would be great, please let’s do that!
@dsyme I have a netstandard2.0 build working in my F# project consuming XPlot in a Windows environment. I don’t do anything in non-Windows. What are you thoughts on calling this v2.0 and releasing to Nuget?
cc @zoranmax @zyzhu