Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why is there no netstandard library for this API? #263

Open
FredBell opened this issue Apr 7, 2019 · 11 comments

Comments

@FredBell
Copy link

commented Apr 7, 2019

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.

@chsriniv9 chsriniv9 added the duplicate label Apr 8, 2019
@chsriniv9

This comment has been minimized.

Copy link

commented Apr 8, 2019

Hi @FredBell

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

@FredBell

This comment has been minimized.

Copy link
Author

commented Apr 11, 2019

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.

@FredBell FredBell closed this Apr 11, 2019
@FredBell FredBell reopened this Apr 11, 2019
@nhustak

This comment has been minimized.

Copy link

commented Apr 20, 2019

I'm glad to see this getting some attention. It's a serious issue in an otherwise extremely nice API.

@nhustak

This comment has been minimized.

Copy link

commented May 24, 2019

Just keeping this thread alive. It's really time to delivery this.

@lxalln

This comment has been minimized.

Copy link

commented Jun 13, 2019

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.

@nhustak

This comment has been minimized.

Copy link

commented Jun 13, 2019

@lxalln I 100% concur with you on this. I am extremely concerned about the lack of movement here.

@jrlang1

This comment has been minimized.

Copy link

commented Jun 13, 2019

1+

@nhustak

This comment has been minimized.

Copy link

commented Aug 5, 2019

Need some feedback on this. Need this ASAP. What do you expect us to do?

@kfallstrom

This comment has been minimized.

Copy link

commented Sep 23, 2019

This needs to happen soon. Please respond.

@nhustak

This comment has been minimized.

Copy link

commented Sep 23, 2019

I called support on this and basically got a non-answer. It's incredibly frustrating that they don't see this as a priority especially when it's fairly simple to get it working.

@fizch

This comment has been minimized.

Copy link

commented Sep 23, 2019

My customers are asking for Stripe integration, so I will probably head that direction instead of waiting on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
7 participants
You can’t perform that action at this time.