QuickOPC User's Guide and Reference
Components and Objects
Fundamentals > Components and Objects
In This Topic

QuickOPC is a library of many objects. They belong into two basic categories: Computational objects provide “plumbing” between OPC servers and your application. They are invisible to the end user. User interface objects provide OPC-related interaction between the user and your application.

Components and Objects in .NET Framework

If you are working with an IDE (Integrated Development Environment) such as Visual Studio, the main QuickOPC components appear in the Visual Studio Toolbox (see example picture below). Note that, however, most QuickOPC objects can be used directly from the code, and that the Toolbox only offers the components for certain environments, such as Windows Forms; in other environments, you can still use QuickOPC, but you will instantiate the components directly. Also note that there are many more objects to QuickOPC than just those classified as designer components and shown on the Toolbox.

The QuickOPC components in the Toolbox look similar to this:

If, for some reason, some or all of the QuickOPC components do not appear in the toolbox, see Troubleshooting Visual Studio Toolbox.

Components and Objects in .NET Standard

In .NET Standard, you instantiate the QuickOPC objects directly, using the constructs available in the language you are using - for a example, the new keyword in C#, the New keyword in VB.NET, etc.

Components and Objects in COM

In QuickOPC-COM, the precise way to instantiate the object depends on the programming language you are using. For example:

 

See Also