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

Support for .net 6 core? #296

Open
inzi opened this issue Nov 21, 2022 · 3 comments
Open

Support for .net 6 core? #296

inzi opened this issue Nov 21, 2022 · 3 comments

Comments

@inzi
Copy link

inzi commented Nov 21, 2022

Will AuthorizeNet be creating a core version of this?

Any suggestions other than refactoring this by hand? Is it just easier to switch to something like spreedly?

@pmarangoni
Copy link

How about .NET Core 7?

@guy9800
Copy link

guy9800 commented Jan 10, 2023

Unfortunately, this repo looks pretty much dead. Also, it seems this is not actually Authorize.Net code. See this comment here #263 (comment)

Not to mention, the full behavior of this API as it is would not translate well into .Net 6. For example, each controller creates an individual HttpRequest object for each REST call. Refactoring this into a set of repositories allowing for generic service registration would be a rather daunting task and quite a bit of code. Understandable that they let a free codebase die with .Net Framework.

However, I will say that, with a bit of effort, an adaptation is not a bidge too far. It would still take a tremendous amount of work on the developer's part, but given things like the cc charge is a flat $0.10/transaction and other processing providers float in the $0.30 range, might be worth considering.

@pmarangoni
Copy link

Wow! I had no idea! Thank you for pointing this out. I gotta say though that I am NOT surprised.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants