QuickOPC User's Guide and Reference
Development Platforms
Introduction > Development Platforms

 QuickOPC supports multiple development platforms. Not all functionality is available on every platform, however. The following table summarizes which functionalities are available where. 

Development Platform Target: COM .NET Framework .NET Standard Excel (with Excel Option)

Runtimes 

.NET Framework

.NET Core

.NET 5 (new in 2021.1)

Operating Systems 

Windows

Linux

macOS (new in 2021.1)

OPC Specifications 

OPC Data Access(2)

OPC Alarms and Events(2)

OPC XML-DA

OPC Unified Architecture - Generic/Data

OPC Unified Architecture - Alarms & Conditions

OPC UA PubSub

Specialized OPC UA Facets 

Methods (Call service)

 (1)

OPC UA Encodings (Client-Server) 

Binary

XML

OPC UA Protocols (Client-Server) 

TCP (opc.tcp)

HTTP

HTTPS

OPC UA PubSub Message Mappings

UADP

OPC UA PubSub Transport Protocol Mappings

UDP (opc.udp)

Ethernet (opc.eth)

Development Models 

Imperative Programming Model

 (1)

Live Binding Model (Windows Forms, WPF)

Live Mapping Model

Reactive Programming Model

Real-time Data Spreadsheet

Features

Browsing Dialogs

 (1)

Browsing Controls (Windows Forms)

Extensions

OPC UA Complex Data

Distribution Formats

Standalone Installer (Windows)

NuGet Packages

Example Archives (TGZ, ZIP formats)

Licensing

License Location

See Licensing Elements

Notes: (1) This functionality is not directly available on the development platform, but can be achieved by combining with VBA code (through COM platform).

Notes: (2) On Windows only.

 

QuickOPC attempts to hide the differences caused by different implementations on various platforms and runtimes from the developer who uses it. It is not, however, always fully possible.

Throughout the documentation, we also try to pinpoint specific areas which are not available under some development platform or may work differently. There may be other, subtle differences under each platform as well. For example, the types of inner exceptions generated by the component may differ under various .NET Standard runtimes versus the code running on .NET Framework, unless the type of exception is documented. The error messages and other details of exceptions may differ as well.

The features discussed here, or some of them, may not be available in all editions of the product. Check the Product Editions page for differences between the editions. The trial license has all features enabled (and is limited in period for which it provides valid data), but licenses for specific commercial editions may have functionality limitations.

'Support' means that QuickOPC is designed to work and tested on the environment, and vendor's technical support may be contacted for assistance with QuickOPC on the environment. Support may be not available for operating systems, .NET runtimes and other dependencies that are past their active lifecycle at the time of support request, even if they were supported at the time of product release.

.NET Standard is basically just an abstract API specification, with multiple runtimes (such as .NET Core) available that fulfill the specification. .NET Framework, on the contrary, is both an API specification and a concrete runtime. Listing them here side by side as two distinct target development platforms might seem improper, but it is not a misunderstanding of the concepts. It is intentional and appropriate, as this is how the QuickOPC usages needs to be distinguished in terms of development and deployment.
See Also