Hello.

In general, we only officially support each QuickOPC version with specific set of operating systems and .NET runtimes. This set is always documented in the User's Guide for the particular version. And, for an overview of how this has evolved over time, you can review the table of versions: kb.opclabs.com/Versions .

.NET 6.0 did not even exist at the time of QuickOPC 2020.2 release, and as such is not officially supported with that version. If you run into problems with such a combination, we will still try to resolve them, but we will "stop" at the moment we suspect that the problem might be due to the unsupported usage.

However, there is no "special code" in the product that would invalidate the license simply because you are using a newer OS, or newer .NET runtime. As such, I would actually expect QuickOPC version 2020.2 to probably work well with .NET 6.0. You have the "Ultimate" edition so that shouldn't be the problem either (Standard edition does not support .NET Core).

But, there is a common trap: When used from .NET Core/.NET 5+ runtimes in QuickOPC versions 2021.3 and earlier, the license stored in the registry (using the License Manager) is not recognized. You need to embed the license in your project, as described in the User's Guide. Starting with version 2022.1, licenses from the registry are also recognized in .NET Core/.NET 5+ (on Windows only - as there is no registry on Linux or macOS).

So I suppose this is the likely cause.

See also:
- opclabs.doc-that.com/files/onlinedocs/QuickOpc/2020.2/User%2.../webframe.html#Licensing3.html
- opclabs.doc-that.com/files/onlinedocs/QuickOpc/2020.2/User%2...esource%20License%20Store.html

Best regards