Add .NET Core support for AF SDK
Please add support for .NET Core to the AF SDK. Currently only full .NET Framework is supported.
Asle Frantzen commented
Any updates to this? It will be a pain if we can't communicate with AF through the SDK in our modern .NET applications.
Any updates? I am getting the question about .NET 5/ .NET Core support for the AF SDK from my colleagues more and more. What can I tell them?
Steve Boyko commented
Is there any update on .NET 5 / .NET Core support for AF SDK? This has been repeatedly asked in PI Square for at least the past 3 years.
See also the request for Linux support at https://feedback.osisoft.com/forums/555145-pi-developer-technologies/suggestions/35508820-af-sdk-and-web-api-on-linux-os-es#comments
Harald Ulriksen commented
So this has been frequently requested since at least 2016. And with the release of .NET 5 it is clear that WCF is not a priority. Meanwhile there has been a massive work on performance on .NET with Span<T>, Pipelines, Kestrel you name it. WCF is NOT even mentiond while Microsoft actively work on GRPC performance and are now at the very top of several Techempower benchmarks.
There are many reasons to support this, ranging from Linux support, performance, security, to just keeping up with the development in the overall .NET ecosystem. It makes it very hard to get OSISoft to play with the other code one is building.
What do we do if there's a security liability in another 3rd party package which requires us to upgrade to .NET Core because they just don't maintain .NET Framework any more? One can't.
The lack of .NET Cor/.NET 5 is quickly becoming a problem. And quite frankly what seems like lack of interest from OSISoft comes across as lack of interest and disregard for the developer story.
Kenneth Barber commented
The title should be changed to say ".NET 5" instead of ".NET Core". .NET 5 was released a few days ago.
Its quite ridiculous that after all of the years .net core is around, we are still stuck using an old version of .net for any custom integration.
It is absolutely imperative that with the slow internal development speed at Osisoft limiting benefits to companies that you provide at least the ability to use the latest tools for us to create interim solutions ourselves.
Jeff Parker commented
Please consider including support for the OSIsoft.PI namespace as well.
Steve Boyko commented
OSIsoft has been moving toward slimming down the PI system for performance and security reasons. Supporting .NET Core is a logical part of that movement.
Please! This is really required for our scenarios when running Linux containers in Kubernetes cluster.
Web App development using new .NET Core technology like Blazor Apps is becoming a new standard agains old "MVC" apps, because of speed, simplicity and UI experience /features
My business opition is that having PI AF SDK supported in such kind of applications is a must for OSISOFT
John Weir commented
We are still using an old Linux SDK for PI. Why? We run all of our services on Linux systems. Switching over to support Windows would be an extra cost for us and added complexity to our processes.
For that reason .NET Core support would be fantastic – or .NET 5 (with Linux supported)
Rick Davin commented
I can live with .NET Core 3.x support. What I really want is AF SDK to be supported in .NET 5.