Microsoft is changing the Api to get HTTP content from version to version. Also the type of possible authentication mechanism behind is changing all the time. So in Universal App for Windows 10, Windows Phone or Windows Store 8 or 8.1. the underlying platform for HTTP access is different in several areas.

System.Net.HttpClient

The System.Net.HttpClient from NuGet that is using the different underlying platforms and therefore is making the same problems. To not being totally confused, it is better not to use System.Net and always use the underlying platform directly instead

Windows.Web.HttpClient or HttpWebRequest

It is better to use one these clients.

Windows Phone 8: HttpWebRequest

Windows 10 and 8.1 should use Windows.Web.HttpClient

Known problems and bugs in Windows.Web.HttpClient or the old HttpWebRequest:

There are some known bugs available but for a lot of them there are work arounds you can use:

If you have any problems by using the included authentication methods (for example: PasswordCredential) you “just” need to do the authentication by your self creating and adding specific request headers.

Hereinafter is a sample showing how these header entries must be used if you need Digest authentication. The sample uses the old HttpWebRequest but you can rewrite the sample to use Windows.Web.HttpClient easily.

Today I was not able to completly shutdown a hyper-v virtual machine keeping a never ending “Stopping..” state. Killing the “Virtual Machine Worker Process” was not possible. After restarting the host machine, the VM was still during stopping… state.

I solved the problem by doing the following.
– Use task manager to end the “Virtual Machine Management Service” task
– In the Hyper-V Manager start the service again
– Now all VM’s seems to be turned off now, but the “Virtual Machine Worker Process” still exists
– Delete the VM in the Hyper-V Manager
– Restart the host machine
– Re add the VM in Hyper-V Manager