Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Why is there no netstandard library for this API? #263
New issue created in hope that someone working on this API can give all of us an official response as to why there is no netstandard library for this API.
As you probably already know, any library for .net should be written for netstandard whenever possible. The benefit is to only write the library once and it can be shared across all .net environments/frameworks. Therefore the cost saving benefits for a netstandard library are pretty obvious.
Some folks in the github community have already ported this sdk-dotnet to netstandard2.0 by themselves. But this is not a solution for the community at large. An official - production ready - netstandard version of the API is required for compliance reasons.
We have been using Authorize.Net as a gateway on a few .net websites for many years.
A company of that size - specially in such a serious space as payment processing - should have this nailed many months ago for sure. But no, thus far they have no solution to this and they have not yet publicly communicated on when will they will release a netstandard library - if at all.
You would think that simply as a mark of respect for their many customers, auth.net would be more transparent regarding such an oversight on their part.
I just don't understand... don't know what else to say... it's nuts.
Thank you for your inputs, kind words and continuous support. This is significantly helping us to prioritize and steer Authorize.Net to deliver incremental value to our developers community and Merchants.
As communicated on the other thread #162 .Net Standard work is in our backlog and will update soon on the release timelines !!
Thanks for your patience
Thank you for your response.
We are all looking forward to the day the netstandard version is released.
About the timeline for the release, can we hope to get the netstandard before the end of May 2019? And a production certified version 1 or 2 months after that?
We also hope the netstandard version will have the same API definitions as the current one. This will simplify future integration work and will make sure everyone uses the same netstandard version moving forward. Since at that point, the framework and core versions will become redundant.
We are currently building our integration with Authorize.NET. I am very disappointed that there is still no netstandard.
I am going to have to write my own API wrapper now, which is going to take me time that I'd rather not spend compensating for the inadequacies of this library.
There really is no excuse for not making this SDK netstandard compliant, it doesn't fill me with any confidence in building a successful working relationship with Authorize.net. There is a reason that Stripe are dominating in this space, and you guys not offering adequate support for dot net developers is making it easy for them.
You have had an open issue for over 2 and a half years, it worries me that your development team don't understand that this is a priority.