QuickOPC User's Guide and Reference
User Interface
The following table shows which functionality is available for different development platforms:
| Development Platform: | COM | .NET Framework | .NET 6+ | Python | Excel (with Excel Option) |
|
Features |
|||||
| OPC Common Dialogs - Windows Forms |
✓ |
✓ |
✓ (4) |
✓ |
⨯ (1) |
| OPC Common Dialogs - Windows Presentation Foundation (WPF) |
⨯ |
✓ (2) |
✓ (2) (4) |
⨯ |
⨯ |
| OPC Controls - Windows Forms |
⨯ |
✓ |
✓ (4) |
⨯ |
⨯ |
| OPC Controls - Windows Presentation Foundation (WPF) |
⨯ |
✓ (3) |
✓ (3) (4) |
⨯ |
⨯ |
| Administer OPC UA Application Dialog |
|
✓ |
✓ (4) |
⨯ |
⨯ |
|
Unsolicited User Interaction |
|||||
| Unsolicited User Interaction - Console |
✓ |
✓ |
✓ |
✓ |
⨯ |
| Unsolicited User Interaction - Windows Forms |
✓ |
✓ |
✓ |
✓ |
✓ |
Note (1): This functionality is not directly available on the development platform, but can be achieved by combining with VBA code (through COM platform).
Note (2): OPC Common Dialogs use the Windows Forms technology, but can be invoked from WPF applications.
Note (3): OPC Common Controls use the Windows Forms technology. A subset of them, wrapped in a WPF control, is made available in WPF.
Note (4):
|
In runtime, all user interface features (such as controls, dialogs, and live binding; Windows Forms and WPF) and nonvisual components are supported both under .NET Framework and .NET 6+. However, "designing" them (this includes tasks like dragging from the Toolbox, or configuring in Properties window) in Visual Studio is only possible in .NET Framework projects. In order to achieve visual design for .NET 6+ projects, the developer can make two project files over the same set of source files, one targeting .NET Framework and one targeting .NET 6+, and use the project that targets .NET Framework for visual design tasks. |