Xamarin Support

[NVentimiglia]

Does Cloudinary support Xamarin mobile clients ? Xamarin uses the mono subset (4.5), not the full .net runtime.

[NVentimiglia]

Update, it is not supported.

After looking at the code it looks like some of the practices are pretty dated (HttpRequest being used instead of an HttpClient). Any plans to update this to a PCL project ?

[eanagel]

+1. This has been open for 16 months, can we get an update?

[roeeba]

It is in our plans to have better support for all popular framework, including a Xamarin SDK. As it is currently not in our immediate plans, we have no ETA to share.

[jamesmontemagno]

Seems like you could just move this over to a .NET Standard library so you could support Xamarin, WPF, .NET, .NET Core, ASP.NET, and tons of other ones too. Might be worth investigating making this investment for all developers.

[jamesmontemagno]

It actually looks like you have a .NET Standard Library already targeting 1.6. Although it has a weird name of "NetCoreShared" it isn't related to .NET Core at all. This actually is consumable in Xamarin.iOS and Android projects as Xamarin Support the 1.6 .NET Standard Library spec.

[NVentimiglia]

The standard library simply does not work. The UploadAsync method never completes. The logs have this.

System.OperationCanceledException: The operation was canceled.

[YomesInc]

Hey guys, replying by the order:

@NVentimiglia

Does Cloudinary support Xamarin mobile clients ? Xamarin uses the mono subset (4.5), not the full .net runtime.

Update, it is not supported.
After looking at the code it looks like some of the practices are pretty dated (HttpRequest being used instead of an HttpClient). Any plans to update this to a PCL project ?

Directly, no – it`s not supported. But –

@jamesmontemagno

Seems like you could just move this over to a .NET Standard library so you could support Xamarin, WPF, .NET, .NET Core, ASP.NET, and tons of other ones too. Might be worth investigating making this investment for all developers.

Yes, this might work across new .net core implementation. No one checked this on our end though.

@jamesmontemagno

It actually looks like you have a .NET Standard Library already targeting 1.6. Although it has a weird name of "NetCoreShared" it isn't related to .NET Core at all. This actually is consumable in Xamarin.iOS and Android projects as Xamarin Support the 1.6 .NET Standard Library spec.

Not exactly. NetCoreShared is a library that targets .net core and this is how it should be used in .net core based projects.

The standard library simply does not work. The UploadAsync method never completes. The logs have this.
System.OperationCanceledException: The operation was canceled.

Not sure what you mean by “standard library”. When we (RTL team) started supporting .net core, we reworked project's structure only and did not touch the code. What you are describing can be a bug that was not included in our scope and lived there for a long time. We'll consult with Cloudinary on this.

[YomesInc]

@NVentimiglia and knowing the version about your last question about standard library could also help.

[jamesmontemagno]

So pulling down the project I saw that it is actually a .NET Standard Library, not a .NET Core Library, which is actually good because .NET Standard Libraries are .NET Libraries that can be consumed by any .NET Application that adhears to the profile selected, in this case 1.6: https://docs.microsoft.com/en-us/dotnet/standard/library

I was able to pull in the library into a Xamarin.Android Project by adding a few other NuGets to it and it compiled just fine, however I didn't actually test out the APIs though, but from what it sounds like it isn't finished yet.

There always seems to be a lot of confusion around .NET Core vs .NET Standard Libraries and how they mesh together..

.NET Core is a .NET Runtime that runs on Windows/Mac/Linux, just like .NET Framework has a .NET Runtime that runs on Windows, and Xamarin has a .NET Runtime that runs on Mac/iOS/Android/Windows/Linux/EverythingElse. Each of them you can create a Class Library for a single platform such as .NET Core or WPF for instance and take advantage of the .NET and Libraries of the platform.

However, since each platform has .NET you ideally want to just write some .NET code and have it be able to be consumed by any of these platforms. That is what a .NET Standard Library does and comes into play. It lays down a contract of what APIs each platform must implement to partake in each version... 1.0, 1.1, ... 1.6, 2.0 for instance. Each version contains more and more APIs, but may lose some platforms such as older windows phone/store devices.

So, if you target .NET Standard 1.6 you get: .NET Core, Xamarin, Mono, and .NET Framework 4.6.1 that can consume your library. Additionally, when the next version of UWP comes out that support .NET Standard 2.0 it can also consume a 1.6 library. These platforms are documented on the GitHub link I sent. Hope that helps.

[YomesInc]

Exactly, @jamesmontemagno We targeted .NET Standard 1.6 to be able to work in .net core and other related projects.

@NVentimiglia Please let me know the version so we'd start working on it.

[NVentimiglia]

@RTLcoil I pulled from master.

Testing on a Xamarin.Forms 2.3.4.247 Android, IOS, and PCL project

[YomesInc]

@NVentimiglia Thank you. Could you also clarify if what was the DLL version used? NetCoreShared or cloudinaryDotNet. Seems it was NetCoreShared, but just want to make sure.

[NVentimiglia]

Yes, NetCoreShared.