Description
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.
We are very familiar with Auth.net and appreciate its services, but we are also growing exceedingly concerned that auth.net does not seem to have much software development capabilities when it comes to their API.
It is a bit frightening to see that they do not have yet a netstandard library already available and production ready.
It is even more frightening to see that they did some work on creating one for netcore which has been in beta for many months). Why would they create a library using netcore? It does not make any sense at all and it looks like they do not understand the .net technology stack and how to use it. I am truly baffled by the lack of quality regarding this API.
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.