The exception that is thrown when an OPC UA result (return value or an argument) was not expected for the requested operation.
Description
Methods
 Equals | Determines whether the specified object is equal to the current object. |
| GetBaseException | Returns the Exception that is the root cause of one or more subsequent exceptions. |
| GetHashCode | Returns a hash code for the current object. |
| GetObjectData | Sets the SerializationInfo with information about the exception. |
| GetType | Gets the Type of the current instance. |
Properties
 DisplayString | The display string for the current object. |
| HelpLink | Gets or sets a link to the help file associated with this exception. |
| InnerException | Gets the Exception instance that caused the current exception. |
| Message | Gets a message that describes the current exception. |
| Source | Gets or sets the name of the application or the object that causes the error. |
| StackTrace | Gets a string representation of the immediate frames on the call stack. |
| TargetSite | Gets the method that throws the current exception. |
| ToString | Returns a string that represents the current object. |
Remarks
The COM objects of QuickOPC 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.
See Also