-
Notifications
You must be signed in to change notification settings - Fork 8
.NET Standard compatibility #1
Comments
Hello! No, the Xamarin Forms Standard version is not .NET Standard compatible - it is a reduced, 'business' version of the full 'professional' version, as you can see here: Steema does have a .NET Standard compatible Charting assembly, however, which is this one: There are also .NET Core versions for Windows Forms and WPF. |
You're welcome! My mistake - the 'pure' .NET Standard assembly is in the following NuGet package: |
great, that's what i was looking for! |
The .NET Feature Matrix is here: The NuGet package I pointed you to is the Pro version - so all of the chart types listed for Pro are available to you. The TeeChart.NETStandard.dll assembly is built in .NET Standard 2.0, meaning it is compatible with all the implementations listed in the table here: I have added an example of how to use TeeChart.NETStandard.dll here: Please note that the TeeChart.NETStandard.dll this example is using is under the 'netstandard2.0' folder - this is because the TeeChart.NETStandard.dll in the NuGet package I mentioned may have problems on instantiating instances of the class 'Chart' on some machines. This problem will be rectified in a future NuGet release. |
Is the Xamarin.Forms package also going to be available for .NET Standard? |
In my understanding from the Documentation: it's not that Xamarin.Forms or any other platform is available for .NET Standard, but rather than the .NET Standard APIs are available to different platforms - this means that the TeeChart.NETStandard.dll can already be used in Xamarin.Forms, as per this page: https://docs.microsoft.com/en-us/xamarin/cross-platform/app-fundamentals/net-standard |
Can you assist me on creating a chart with the net-standard package? Kind Regards, |
We are presently preparing an example of how to use TeeChart.NETStandard with Xamarin.Forms and will advise you when it is ready. |
Great, thanks in advance! Greetings Bluekuen |
We plan to have it ready for you before 12h tomorrow. |
That's perfect, appreciate it! |
Unfortunately we are not going to be able to provide you with the example we promised. The issue is a technical one - TeeChart.NETStandard.dll - our .NET Standard 2.0 compatible TeeChart library - references the NuGet package System.Drawing.Common. This means that when TeeChart.NETStandard.dll is referenced in a Xamarin.Forms project, it will throw an error identical to the one described here. Of course we will be looking into this issue in more depth, but this does mean that we cannot provide you with the example you requested at this time. |
Alright, thank you for the information! |
Hello, i'm back from vacaion and curious if you could already make progress with the .NET Standard version? Kind regards, |
Hello! we're due to have a meeting today to discuss progress on this issue; some has been made, but we are still quite a way from releasing anything to the public. I'll get back to you with something more definite later today. |
Hello, alright, thanks for the information! Kind regards, |
Hello, whoops, by 'today' I must have meant 'within the next 24 hours'! Apologies. Yesterday we concluded that we would commit to the production of a .NET Standard assembly compatible with Xamarin Forms. We hope that within the next three weeks we will have a beta version we can made available for testing. |
Hello bluekuen, |
Hello PepJorge, these are great news! We will test it immediately! Kind regards |
Hello Bluekuen, Thanks Best regards ! |
Hello,
i'm currently testing your plugin for my company and i'm curious now if it's really .NET Standard compatible.
My superior told me to only look for .NET Standard compatible libraries and whilst testing i get following warning with the .NET Standard package:
Is there going to be an update of this package or am i missing something?
We are serious about purchasing your product but it has to be compatible with .NET Standard.
I'm looking forward for an answer!
Kind regards,
bluekuen
The text was updated successfully, but these errors were encountered: