Support 10586/14393 Windows Mobile

[hpsin]

trafficstars

Due to the cookie-based authentication scheme on phone's Device Portal, the Basic-Auth scheme used by the Wrappers library isn't compatible.

[zabulus]

Will you accept PRs for this issue?

[hpsin]

Absolutely! It's been lower on our priority list while we finish out the API surface, but would certainly welcome the contribution!

[zabulus]

In my project I've already used RestSharp to communicate with Device Portal.

while we finish out the API surface

Any details about this?

[hpsin]

We've got a couple more APIs to finish before v1.0 - see the milestone here: https://github.com/Microsoft/WindowsDevicePortalWrapper/milestone/2 Specifically, Xperf, ETW, and WER APIs.

Did RestSharp handle the PIN pairing and CSRF protection? That would be interesting to investigate. Thanks! Hirsch

[zabulus]

Did RestSharp handle the PIN pairing and CSRF protection? That would be interesting to investigate. Thanks! Hirsch

It's just cookies taken from here and there.

EDIT: or you wondering about API sequence call?

[NGame1]

Isn't there any fix for this issue ? I really need it for my next project

[zabulus]

I can only provide you implementation of API client on top of RestSharp, used in BenchmarkDotNet: https://github.com/dotnet/BenchmarkDotNet/blob/uap/src/BenchmarkDotNet.Toolchains.Uap/Toolchains/Uap/DevicePortalApiWrapper.cs It just covers deploying and starting application and handles authentication for both mobile and PC device portals implementation (difference in authentication method)