Open JakePorter05 opened 1 year ago
I suggest avoiding this package at all costs. If you must use Authorize.net, just hit their API with an HttpClient. Better yet, use Braintree or something else. Authorize.net has the industry's worst documentation and worst support. They gave up a long time ago.
When we migrated most of our projects from .Net 4.5 to .NET Core 6, I used this fork of the .NET Core beta: https://github.com/Michaelogical/dotnet-core-sdk-beta
We have not had any issues with it after 2 years of use but we are currently only using it for signups, the rest of our billing code still runs on .NET 4.5 using this older SDK.
We have not been happy with the state of Auth.net so we migrated most of our clients to Stripe but we still have some integrations that require Auth.net so we are stuck supporting it for now.
I am getting ready to use AuthorizeNet in a new Blazor .net 7 web server. It seems to still work if I manually also add System. Configuration.ConfigurationManager. Are there any issues with trying this? Or is there an updated Nuget version that is compatible with .net 7?