Look at the use of Microsoft.AspNet.WebApi.Client package from 2018 in some components (Events)

[SandGrainOne]

Description

The Microsoft.AspNet.WebApi.Client package is getting old. The last version of the package was released in 2018. It's used by at least one component and this is Events, but there might be more. We use it for it's extension methods on HttpContent to deserialize http responses, but there might be more.

The package has a dependency to Newtonsoft.

Up to date extension methods can be found in the System.Net.Http.Json namespace.

Specification tasks

• Development tasks are defined

Development tasks

Test

Definition of done

• Documentation (docs.altinn.studio) is updated (if relevant)
  • Technical documentation
  • User documentation
• QA
• Manual test is complete (if relevant)
• Automated test is implemented (if relevant)
• All tasks in this userstory are closed (i.e. remaining tasks are moved to other user stories or marked obsolete)

[altinnadmin]

Is there a good reason for not using the extension methods in these classes instead?

https://docs.microsoft.com/en-us/dotnet/api/system.net.http.json

[SandGrainOne]

Is there a good reason for not using the extension methods in these classes instead?
https://docs.microsoft.com/en-us/dotnet/api/system.net.http.json

I did mention that namespace in the desciption:

Up to date extension methods can be found in the System.Net.Http.Json namespace.

I just wasn't aware of it when I created this issue. (Despite having used it for the JsonContent class.)

[SandGrainOne]

Moved the issue to the platform repository:
Altinn/altinn-events#246