Hello.

We reference only the NuGet packages we absolutely need. And we need to find a balance between not choosing versions that are too old (and might have bugs, be deprecated etc.), and versions that are too new (because that would require our users to upgrade, and they may not like it).

Many references are pulled in indirectly, and we have no control over them. This is especially the case with OPC UA stack from OPC Foundation, which is probably what is at the heart of your post.

This said, I will try to address the issues in your report:

1) You wrote that "a lot of Net Core nugets loaded too" [in .NET Framework 4.8 project]. I do not understand what you mean. The NuGet packages being referenced are not specific to .NET Core or .NET Framework. They cover multiple targets, and *inside* each NuGet package, there are/might be different assemblies or further references for different targets.

2) You wrote "Many of the updates fail". Cannot reproduce it. I created a new .NET Framework 4.8 (console) project, and added OpcLabs.QuickOpc version 5.71.334 to it. It goes without error.

3) "many deprecated Nugets" - I am seeing just one (Microsoft.Extension.PlatformAbstractions). Will look at it, but there is no newer version, so we might be forced to stay with it.

Regards