Consume new Microsoft.AspNet.WebApi.Client.5.2.4 package

[dougbu]

Our Microsoft.AspNetCore.Mvc.WebApiCompatShim package currently has an indirect dependency on the Microsoft.Net.Http package. Building the shim project requires imports when targeting .NET Standard for the same reason. Both issues could be avoided if we moved to the latest Microsoft.AspNet.WebApi.Client package.

See also

• ASP.NET Core & System.Net.Http.Formatting #5562, an older report of related problems
• Publish at least the Microsoft.AspNet.WebApi.Client.5.2.4 package AspNetWebStack#45, tracking publishing the Microsoft.AspNet.WebApi.Client v5.2.4 package for realsies
• Add netstandard support to appropriate packages AspNetWebStack#4, which covered adding .NET Standard 1.1. support to the Microsoft.AspNet.WebApi.Client package
• the current Microsoft.AspNetCore.Mvc.WebApiCompatShim package
• the current Microsoft.AspNet.WebApi.Client package
• the new Microsoft.AspNet.WebApi.Client package

[Eilon]

This is approved, but let's figure out the plan to actually ship the 5.2.4 wave of packages.

[dougbu]

Should I go ahead with this in the meantime i.e. with the nightly ASP.NET feed in MVC's NuGet.config?

[Eilon]

We should talk about how to do the release and see if we can just do that.

[dougbu]

Side note: Fix here should include removing the last couple of $(PackageTargetFallback) aka "imports" from the MVC repo.

[Tornhoof]

Any plans for a public aspnet/AspNetWebStack?
Just asking as aspnet/AspNetKatana ist already public and some issues in aspnet link the private repo

[dougbu]

The first priority is to publish 3.2.4 / 5.2.4 packages from aspnet/AspNetWebStack or at least the Microsoft.AspNet.WebApi.Client.5.2.4 package on NuGet. But, yes, work to make that repo public is in progress.

[JunTaoLuo]

@Eilon were we going to remove this package? Is there an issue tracking that?

[Eilon]

Oops forgot to log an issue. I'll start a thread first. I'll actually go do that now.