OPC Labs EasyOPC “Classic” Library
Project Overview
Description
OPC Labs EasyOPC “Classic” Library

 

TLBID (Type Library ID): 1F165598-2F77-41C8-A9F9-EAF00C943F9F
Assembly: OpcLabs.EasyOpcClassic, Version=5.80.82.1, Culture=neutral, PublicKeyToken=6faddca41dacb409

 

For more information, see OpcLabs_EasyOpcClassic in .NET Reference.

Classes
Class ModuleDescription
The EasyAEClient object is the main object that allows simple access to OPC Alarms and Events servers.
Allows static management and configuration of the EasyAEClient object.
The EasyDAClient object is the main object that allows simple access to OPC Data Access servers.
Allows static management and configuration of the EasyDAClient object.
Describes how to select the EasyAEClient object.

 

ProgId: OpcLabs.EasyOpc.AlarmsAndEvents.EasyAEClientSelector
CLSID (Class ID): 3d27401a-d104-4c09-96a6-372d63671a7b
Default interface: OpcLabs.EasyOpc.AlarmsAndEvents.ComTypes._EasyAEClientSelector
Event source interface:

 

For more information, see EasyAEClientSelector and OpcLabs.EasyOpc.AlarmsAndEvents.ComTypes._EasyAEClientSelector in .NET Reference.

Describes how to select the EasyDAClient object.

 

ProgId: OpcLabs.EasyOpc.DataAccess.EasyDAClientSelector
CLSID (Class ID): 4ebce08f-82bb-4685-ac7f-d597bd956b41
Default interface: OpcLabs.EasyOpc.DataAccess.ComTypes._EasyDAClientSelector
Event source interface:

 

For more information, see EasyDAClientSelector and OpcLabs.EasyOpc.DataAccess.ComTypes._EasyDAClientSelector in .NET Reference.

Remarks
This documentation is for COM interface to OPC Data Client (for use from tools such as VB6, VBA, Delphi, PHP etc.). If you are developing in .NET, use a direct link in this article to navigate to the corresponding .NET content, or visit .NET Assemblies Reference for an overview of available .NET reference parts.

The COM objects of OPC Data Client are based upon the underlying .NET objects. In order to avoid duplicities and mismatches, the documentation is primarily maintained for the .NET objects. The .NET objects are exposed using the "interop" mechanism to the COM world using an automated translation provided by Microsoft. Therefore, a documentation that applies to a .NET type or member that is exposed to COM can be assumed to apply to the corresponding .NET type or member as well.

The bulk of the reference documentation for COM type libraries is generated from the type libraries themselves. This means that only a limited descriptive text (typically, one line) is available with each type or member. You need to look to the reference documentation for the .NET assemblies in order to find the more detailed documentation.

In addition, some languages or COM-based tools do not make direct use of the type libraries, and therefore require some additional effort to use the COM objects - such as knowing their ProgIDs, dealing with interface IDs (IIDs), etc.

For more information, see COM Type Libraries Reference.