Restsharp: Some packages are not compatible with UAP,Version=v10.0

There is no support for this project type yet.

Is there any plans in the near future?

Not right now no but I'll add this as a feature request.

I came here looking for this. It would be great to have UWP support since that seems _the_ way from now on.

It's still very new. I'll see what I can do to get it in. My development environment isn't windows 10 yet so it will have to wait for that change to happen.

Yeah, would be great to have Win 10 UWP support. There are only a couple of decent REST wrappers for .Net out there - this one and PortableREST.

no problem. i'm working on getting a windows 10 environment set up so this can happen.

That's a great news to hear. I'll be waiting for this update. :+1:

I just want to say +1... I'd love to have RestSharp for my UWP projects.

@hallem Any updates on this issue?

I've the same problem.

Want support for UWP too please!

+1

+1

+1

+1

+1

+1

+1 Any updates?

+1

code for UWP support has been checked into master but nuget support is still pending. i or the PR author need to add the targeting to the build scripts

@hallem Thanks, but this only works for x64 and x86 while it does not work for ARM-devices (e,g. Windows 10 Mobile), any plans for that?

Is the API now ready for ARM?

@weird-dreams Still waiting for a statement of @hallem , hopefully it will be added soon :)

Please support ARM - we are building a continuum experience on a ARM device!

please support "_UAP,Version=v10.0_" fully (x86,x64,ARM).
Swagger creates good proxies but they do not work on my phone + desktop (continuum!) without RestSharp.

+++++1

+1

+2

@jerry1621 any chance you could share the modifications you made as referenced in the swagger-codegen thread? I attempted to copy your steps but it's not working.

@emigrating sure: I just edited the build.bat and added a few lines for UWP
e.g. there are these download-directories created by:
if not exist Download\package\lib\net35 mkdir Download\package\lib\net35\ if not exist Download\package\lib\net4 mkdir Download\package\lib\net4\ if not exist Download\package\lib\net4-client mkdir Download\package\lib\net4-client\ if not exist Download\package\lib\net45 mkdir Download\package\lib\net45\ [...]

so just add a line for uwp, too
if not exist Download\package\lib\uwp mkdir Download\package\lib\uwp\

Simply complete the build.bat by adding uwp-statements to the other statements

What we can do to support UWP?

+1

+1

+1

+1

Still no support for UWP apps on an ARM device?
Please invest some time in supporting this...
Thank you!

Still no support....

We will only support .NET Standard 2.0. UWP that is compatible with .NET Standard is in preview.

But .net standard 2.0 support for RestSharp isn't released yet is it? Tried to use it in a .net Core 2.0 project before and it was broken. Is a pre-release for that available somewhere?

It is in preview too, from today. Would be great if you can test. https://www.nuget.org/packages/RestSharp/106.0.0-alpha0277

UWP & .NET Standard 2.0: A preview is now available
https://blogs.msdn.microsoft.com/dotnet/2017/08/25/uwp-net-standard-2-0-preview/

We will support UWP as any other platform by supporting .NET Standard 2.0. There will be no separate package for UWP.

Absolutely great, thanks!

{System.PlatformNotSupportedException: Operation is not supported on this platform.
   at System.Net.SystemWebProxy.GetProxy(Uri destination)
   at System.Net.ServicePointManager.ProxyAddressIfNecessary(Uri& address, IWebProxy proxy)
   at System.Net.ServicePointManager.FindServicePoint(Uri address, IWebProxy proxy)
   at System.Net.HttpWebRequest.get_ServicePoint()
   at RestSharp.Http.ConfigureWebRequest(String method, Uri url)
   at RestSharp.Http.GetStyleMethodInternal(String method)
   at RestSharp.Http.AsGet(String httpMethod)
   at RestSharp.RestClient.DoExecuteAsGet(IHttp http, String method)
   at RestSharp.RestClient.Execute(IRestRequest request, String httpMethod, Func`3 getResponse)}

Well, they are in preview, expect things to improve closer to release. You can also help them by submitting issue reports.

But we also plan moving to HttpClient, but this work is not easy. I have tried but then decided to postpone it. If some is willing to help - please, submit a PR. With HttpClient things will be more compatible.

I'll take a look at the current code and see if I can do anything to help with the change to HttpClient.

The alpha version is being published from develop branch. Most probably I will have to release as-is with web request. HttpClient can be done right after that. I would prefer the work on HttpClient replacing WebRequest to be started in a fork or separate branch. But literally this is days of work, not hours.

@mavanmanen it seems like a general issue, please switch to #992 to continue the discussion