Answered

NuGet package Microsoft.PowerPlatform.Dataverse.Client v1.1.16 references .NET 7 library

(0) Share

Report

Posted on by Henk van Boeijen

NuGet package Microsoft.PowerPlatform.Dataverse.Client v1.1.16 (and v1.1.17) has a dependency on System.Test.Json v7.0.3, which is part of .NET 7.0. It should reference System.Test.Json v6.0.7, as v1.1.14 does.

This is causing issues in our Azure functions.

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (3)

Answers (1)

Sort by

cchannon 4,702 Moderator on at

Like (0)

Report
Copy link

Link copied!

@MattB-MSFT is this still in your bailiwick?

Was this reply helpful? Yes No
Verified answer

MattB-MSFT Microsoft Employee on at

Like (2)

Report
Copy link

Link copied!

Yep, this has been posted about and discussed here: https://github.com/microsoft/PowerPlatform-DataverseServiceClient/discussions/424

long story short, this was done to comply with security issues in the 6.x versions of system.json.text and its dependencies.

the lib is usable back to full framework, azure functions has not picked up the change yet. Or they solved it a different way. The linked article describes how to allow azure functions to accept the updated lib

Was this reply helpful? Yes No
Henk van Boeijen 6 on at

Like (0)

Report
Copy link

Link copied!

Thanks for your reply! I still find it hard to see how introducing a dependency to .NET 7.0 would be a good idea in the first place. Since NuGet package Microsoft.PowerPlatform.Dataverse.Client did not come with a major or minor version upgrade we did not expect breaking changes being introduced. Unfortunately our unit tests could also not save us here.

Any chances this change will be reverted in the future? Or should we wait for .NET 8.0 support?

Was this reply helpful? Yes No