Investigate using System.Net.Http.HttpRequestMessage about azure-functions-powershell-worker HOT 4 CLOSED

cc: @asavaritayal

from azure-functions-powershell-worker.

Thanks for the suggestion!

We actually had a long discussion about this. The problem is, HttpRequestMessage isn't useful without all of the helper functions that are supplied in ASP.NET.

Here are the docs for HttpRequestMessage that exists in .NET Core 2.1:
https://docs.microsoft.com/en-us/dotnet/api/system.net.http.httprequestmessage?view=netcore-2.1

There's not much in there.

We would have to bring in ASP.NET Core to really get any benefit and we'd like to not have to do that:
https://docs.microsoft.com/en-us/dotnet/api/system.net.http.httprequestmessageextensions?view=aspnetcore-2.1

Also, there's a not-so-friendly behavior in PowerShell where extension methods are not accessible via:

$foo.MyExtensionMethod()
The only way to use extension classes is to do something like:
[MyExtensionClass]::MyExtensionMethod($foo)

These things considered, it was a better experience for the user if we had our own type.

from azure-functions-powershell-worker.

cc: @paulbatum , @mathewc
Thanks for the explanation

from azure-functions-powershell-worker.

I'm going to close this - feel free to drop any questions or comments here and I'm happy to re-open.

from azure-functions-powershell-worker.