Difference between revisions of "What's new in QuickOPC 2021.1"
Jump to navigation
Jump to search
(Created page with "Category:What's New <div style="text-align: right; direction: ltr; margin-left: 1em;">See also: Versions; Previous version: What's new in QuickOPC 2020.3</div>...") |
|||
| Line 34: | Line 34: | ||
=== Specialized Client Objects === | === Specialized Client Objects === | ||
=== Other === | === Other === | ||
| + | --> | ||
== Component Refactorings == | == Component Refactorings == | ||
=== OPC Classic === | === OPC Classic === | ||
| + | * Boxing of client-side OPC proxies/stubs is now also available in .NET Core (on Windows), not just in .NET Framework. This means that if your .NET Core application is using OPC Classic, it does not require "OPC Core Components" as a prerequisite. | ||
| + | <!-- | ||
=== OPC UA === | === OPC UA === | ||
=== COM Components === | === COM Components === | ||
Revision as of 09:24, 26 November 2020
See also: Versions; Previous version: What's new in QuickOPC 2020.3
Internal version number: 5.60
Key changes:
Component Refactorings
OPC Classic
- Boxing of client-side OPC proxies/stubs is now also available in .NET Core (on Windows), not just in .NET Framework. This means that if your .NET Core application is using OPC Classic, it does not require "OPC Core Components" as a prerequisite.
