CODEWITHSUNDEEP
asp.net-core-3.0.net-core-3.0
kpocrz
kpocrz

Reputation: 554

Migrating .NET Core 2 to .NET Core 3: HttpContent does not contain a definition for "ReadAsAsync"

I am following this guide https://learn.microsoft.com/en-us/aspnet/core/migration/22-to-30?view=aspnetcore-3.0&tabs=visual-studio to migrate to .NET Core 3.

I am getting the compilation error:

Error CS1061 'HttpContent' does not contain a definition for 'ReadAsAsync' and no accessible extension method 'ReadAsAsync' accepting a first argument of type 'HttpContent' could be found (are you missing a using directive or an assembly reference?)

The project is a class library, I have updated its csproj removing a package reference to Microsoft.AspNetCore.App and adding a framework reference instead:

  <ItemGroup>
    <FrameworkReference Include="Microsoft.AspNetCore.App" />
  </ItemGroup>

Any ideas why this is happening?

Upvotes: 44

Views: 27469

Answers (4)

Ashique Razak
Ashique Razak

Reputation: 685

Install package System.Net.Http.Formatting.Extension from NuGet. You'll sometimes have to Install Newtonsoft.Json as well, if not existing.

Upvotes: 0

Daniel Congrove
Daniel Congrove

Reputation: 3679

Since System.Text.Json does not support "Allow non-string JSON values for string properties" and I was unable to find or write my own reliable JsonConverter to accomplish this, continuing to use Newtonsoft.Json saved a lot in my case.

In my solution, Microsoft.AspNet.WebApi.Client isn't necessary, just Newtonsoft.Json.

Original Code:

return await response.Content.ReadAsAsync<MyClass>();

.NET Core 3 Solution:

return JsonConvert.DeserializeObject<MyClass>(await response.Content.ReadAsStringAsync());

Upvotes: 6

Chris Pratt
Chris Pratt

Reputation: 239430

ReadAsAsync is a .NET Standard extension that's actually shared between ASP.NET Core and ASP.NET Web Api (via a NuGet library). However, it uses JSON.NET to do the deserialization, and as of .NET Core 3.0, ASP.NET Core now uses System.Text.Json instead. As such, this library (and the extension it contains) is not included in the .NET Core 3.0 framework because doing so would require including the JSON.NET library in addition to System.Text.Json.

While you can manually add the Microsoft.AspNet.WebApi.Client (and Newtonsoft.Json along with it), you should just move on without it. It doesn't save you much anyways, as you can accomplish the same via just:

await JsonSerializer.DeserializeAsync<MyType>(await response.Content.ReadAsStreamAsync());

If you like, you can add your own extension to HttpContent to wrap this up in a ReadAsAsync method:

public static class HttpContentExtensions
{
    public static async Task<T> ReadAsAsync<T>(this HttpContent content) =>
        await JsonSerializer.DeserializeAsync<T>(await content.ReadAsStreamAsync());
}

Upvotes: 82

RoguePlanetoid
RoguePlanetoid

Reputation: 4576

ReadAsAsync is deprecated as being part of .NET Core as of .NET Core 3.0 however you can include it as from the NuGet package Microsoft.AspNet.WebApi.Client and you'll be able to use ReadAsAsync again. When updating web application from .NET Core 2.0 to .NET Core 3.0 I experienced the same issue.

Upvotes: 17

Related Questions