Difference between revisions of "What's new in OPC Studio 2024.2"

From OPC Labs Knowledge Base
Jump to navigation Jump to search
(8 intermediate revisions by the same user not shown)
Line 10: Line 10:
 
= Fundamentals =
 
= Fundamentals =
 
= Nomenclature =
 
= Nomenclature =
 +
-->
 
= Targeting =  
 
= Targeting =  
 +
* .NET 7 is no longer supported (Microsoft end of support May 14, 2024), but will likely work. .NET 6 and and .NET 8 continue to be supported.
 
= Technology =
 
= Technology =
 +
* OPC UA Client-Server parts are now based on OPC Foundation UA-.NETStandard 1.5.373.121.
 +
<!--
 
= Licensing =
 
= Licensing =
 
= Packaging =
 
= Packaging =
Line 18: Line 22:
 
= Installation and Uninstallation =
 
= Installation and Uninstallation =
 
* The Setup wizard now offers a choice of "express installation" for Python development. When selected, only the setup components relevant for Python developers are installed.
 
* The Setup wizard now offers a choice of "express installation" for Python development. When selected, only the setup components relevant for Python developers are installed.
 +
<!--
  
<!--
 
 
= Component Improvements =
 
= Component Improvements =
 
== OPC Classic ==
 
== OPC Classic ==
Line 29: Line 33:
 
== OPC UA Complex Data ==
 
== OPC UA Complex Data ==
 
== OPC UA File Transfer ==
 
== OPC UA File Transfer ==
 +
-->
 
== OPC UA PubSub ==
 
== OPC UA PubSub ==
 +
* The "tls" scheme can now be used in resource addresses, and is equivalent to "mqtts" or "ssl".
 +
<!--
 
== COM Components ==
 
== COM Components ==
 
== User Interface ==
 
== User Interface ==
Line 70: Line 77:
 
== Demo Servers and Publishers ==
 
== Demo Servers and Publishers ==
 
== License Manager ==
 
== License Manager ==
 +
-->
  
 
== OpcCmd Utility ==
 
== OpcCmd Utility ==
 
=== OPC UA Client-Server ===
 
=== OPC UA Client-Server ===
 +
* The '''uaClient collectSoftwareInfo''' command now also collects the new server capabilities introduced in OPC UA 1.05 (such as MaxSessions, MaxSubscriptions, etc.).
 +
<!--
 
=== OPC UA PubSub ===
 
=== OPC UA PubSub ===
 
=== Common ===
 
=== Common ===
Line 83: Line 93:
 
= Examples =
 
= Examples =
 
== Platform: .NET ==
 
== Platform: .NET ==
* Wherever feasible, converted the C# and VB.NET example projects for Console to the "multi-target" format, allowing them to be built for and run on either .NET Framework 4.7.2+, or .NET 6+.
+
* Wherever feasible, converted the C# and VB.NET example projects for Console and Windows Forms to the "SDK" (multi-target) format, allowing them to be built for and run on either .NET Framework 4.7.2+, or .NET 6+.
 
<!--
 
<!--
 
== Platform: COM ==
 
== Platform: COM ==
Line 95: Line 105:
  
 
-->
 
-->
 +
 
= Documentation and Help =
 
= Documentation and Help =
* Moved all Python (.NET) examples to their own group, separate from .NET and COM.
+
* Significantly improved the reference documentation.
 
<!--
 
<!--
 
== COM Components ==
 
== COM Components ==

Revision as of 18:16, 25 April 2024

See also: Versions; Previous version: What's new in OPC Studio 2024.1

Internal version number: 5.81

Key changes:


Targeting

  • .NET 7 is no longer supported (Microsoft end of support May 14, 2024), but will likely work. .NET 6 and and .NET 8 continue to be supported.

Technology

  • OPC UA Client-Server parts are now based on OPC Foundation UA-.NETStandard 1.5.373.121.

Installation and Uninstallation

  • The Setup wizard now offers a choice of "express installation" for Python development. When selected, only the setup components relevant for Python developers are installed.

OPC UA PubSub

  • The "tls" scheme can now be used in resource addresses, and is equivalent to "mqtts" or "ssl".

OpcCmd Utility

OPC UA Client-Server

  • The uaClient collectSoftwareInfo command now also collects the new server capabilities introduced in OPC UA 1.05 (such as MaxSessions, MaxSubscriptions, etc.).

Examples

Platform: .NET

  • Wherever feasible, converted the C# and VB.NET example projects for Console and Windows Forms to the "SDK" (multi-target) format, allowing them to be built for and run on either .NET Framework 4.7.2+, or .NET 6+.

Documentation and Help

  • Significantly improved the reference documentation.