-
Notifications
You must be signed in to change notification settings - Fork 43
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
Is this SDK still being worked on? #16
Comments
Come on guys. Need this to be finalized... |
I am dumbfounded to see that this has not moved to .Net Standard and they have literally made no progress since July of last year. This is the only dependency I have that is keeping me from upgrading to a .Net Core run time for some apps. |
Stripe has one. Moving half of my business to them for new app. If this isn't released soon I'll be moving the rest as well. |
Authorize seems to be having all kinds of problems. We've been having frequent time outs during our calls. Support is unresponsive. HOW many years now without a CORE or STANDARD SDK? It's sort of a joke at this point. |
@aamir-munir, yes, that fork is .NET Standard 2.0.
|
This is also blocking our team from upgrading to .NET Core. Would be really nice to see some activity on this. |
@RobARichardson Good luck. They have pretty much been unresponsive for years now. It is beyond me how they can simply chose to ignore CORE. I finally took the non-core version and converted it myself. We are going to leave them as soon as it's practical - it's not like there's a shortage of competitors. You get what you pay for and we all know they are the cheapest. |
Is this SDK still being worked on?
When should we expect this to be released to NuGet as a Package?
The text was updated successfully, but these errors were encountered: