.Net Core support?

[im1dermike]

Any plans to port this to .Net Core?

[mootrichard]

We do not have any immediate plans to extend support for .NET Core, but we are always open to looking into different ways we can help developers integrate. Currently we only support .NET 4.5 and .NET 4.0.

[CampsiteHelper]

2nd this. showstopper for us

[HakanL]

Yea nowadays library developers should support .NET Standard (the lower version the better) so it can be used both with .NET Core and the full framework.

[HakanL]

I made a fork where I re-wrote this to use .NET Standard 1.3 and started to clean up the interface as well (not using Hashtables, etc). Check it out: https://github.com/HakanL/shippo-csharp-client

Also uploaded to NuGet: https://www.nuget.org/packages/Haukcode.GoShippo

I'm in the process of testing it out so I'm sure there are a few issues.

[mootrichard]

😲 first the Ruby client gets some love and now this! I am over the moon right now! I literally just got done fixing some methods and objects on this library just to get it workable, but having this work in .NET Standard would be so much better

[HakanL]

Note that the API (signatures) has changed quite a bit in my fork, I wanted it to support async calls (using HttpClient instead of WebRequest), plus I disliked the Hashtables (hello .NET 1.0 circa 2002...). There will be a few more changes to get rid of the last Hashtables (IDictionary<string, object> that I changed it to temporarily).

[mootrichard]

I am fully onboard with async support and killing the Hashtables. Dictionaries are faaaar better to work with.

[im1dermike]

@HakanL Thanks for contributing to this issue. Former Active employee here and recognize your name. I used to work under James F.

[HakanL]

Ahh, cool!

[sdulloor111]

I made a fork where I re-wrote this to use .NET Standard 1.3 and started to clean up the interface as well (not using Hashtables, etc). Check it out: https://github.com/HakanL/shippo-csharp-client

Also uploaded to NuGet: https://www.nuget.org/packages/Haukcode.GoShippo

I'm in the process of testing it out so I'm sure there are a few issues.

Is this package now complete and tested for any version of .Net Core?

[HakanL]

Is this package now complete and tested for any version of .Net Core?

I've been using it in production for many months now (currently in .NET Core 3.1).

[aleksbor]

Are there plans to support .Net Core?