Support for netstandard2.0 and net5.0 are missing

[ManfredLange]

There have been pull requests in the past. However, those have not been merged, let alone have they been made available as a new official version.

Is there anyone at eWay watching this repository and then doing something about this?

I am working with a client and this has now reached a point where the client needs to move to .NET Core 3.1 and then on to .NET 5.0. eWay.Rapid does not allow this and causes compile errors.

My client is therefore now considering to move to a different payment provider as it appears to them that eWay is not maintaining this client library.

My view: I think you are at risk losing customers to competitors who keep their client side libraries up-to-date. One such competitor is Stripe. Their client library is also available as a nuget package at https://www.nuget.org/packages/Stripe.net/ with the associated repository at https://github.com/stripe/stripe-dotnet Stripe's support of the developer community appears to be more active.

So what is an ETA for support of netstandard2.0 and net5.0? Or what is your recommendation if those are not happening any time soon? Is there a replacement library that can be used instead that you'd recommend?