NU1605 Warning (As Error) in latest Visual Studio on .NET8 and .NET9 Windows

With Visual Studio version 17.12.5 and using .NET 9, and attempting to update PureCloudPlatform.Client.V2 to any version greater then v216, Visual Studio will generate a NU1605 WarningAsAnError during the update attempts for the following dependencies:

PureCloudPlatform.Client.V2 218.0.0 -> System.Text.Json 8.0.4 -> System.Text.Encodings.Web (>= 8.0.0)
PureCloudPlatform.Client.V2 218.0.0 -> System.Text.Encodings.Web (>= 7.0.0)

Version 216 works fine on downgrade and we can still upgrade to v227 once the default Visual Studio setting for TreatWarningsAsErrors is set to false and do the upgrade after. Microsoft doesn't recommend doing this as per this link - NuGet Warning NU1605 | Microsoft Learn , but it so far appears to work.

What I would like to request on the next release for PureCloudPlatform (i.e. v228) is to also update the dependencies for System.Text.Json and System.Text.Encodings.Web for the latest versions available.

I would create a bug(?), but the support team told me to post in the Dev Forum first.

Hello Damon,

I'll open a ticket for the SDK. I'll talk to the team and update this post once I have some news.

Regards,

1 Like

Hello,

A new version of the SDK (228) has been released today, with an update of the dependencies. Let me know if that solves your issue (or if I have introduced another one :slight_smile: ).

Regards,

Hi

In my case is not working :frowning:

I am using VS Community Edition

Regards

You are talking about a different thing.
In your case, it is not preventing the build - it is a warning.
The ini-parser takes care of the configuration file (if you use such with the .Net SDK - not mandatory) - See Configuration file.
This third party library is not supported with .Net 8.0/.Net 9.0.
So the warning is just telling you that capabilities related to the ini-parser may not be functional. Meaning that with .Net 8.0/.Net 9.0, you will not be able to set a configuration file.
All other features/capabilities will be functional.

For info, some other exchanges in the past on ini-parser that may provide more context: here and here

Regards,

1 Like

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.