What's new in OPC Studio 2025.2: Difference between revisions

From OPC Labs Knowledge Base
 
(4 intermediate revisions by the same user not shown)
Line 17: Line 17:
<!--
<!--
= Licensing =
= Licensing =
-->
= Packaging =
= Packaging =
* Separated low-level '''OpcLabs.Core''' and '''OpcLabs.Core.Forms''' NuGet packages for reuse. This change is largely invisible to the developer; you keep referencing the same high-level NuGet packages as before, and the new packages get automatically referenced transitively.
<!--
= Delivery =
= Delivery =
= Installation and Uninstallation =
= Installation and Uninstallation =
-->
= Component Improvements =
= Component Improvements =
<!--
== OPC Classic ==
== OPC Classic ==
== OPC Data Access and OPC XML-DA ==
== OPC Data Access and OPC XML-DA ==
Line 31: Line 37:
== OPC UA Complex Data ==
== OPC UA Complex Data ==
== OPC UA File Transfer ==
== OPC UA File Transfer ==
-->
== OPC UA PubSub ==
== OPC UA PubSub ==
* The custom connection property "0:MqttTopicPrefix" is interpreted as the <Prefix> part of the topic convention.
* More relaxed decoding of JSON messages, allowing to process messages from publishers not fully conforming with the OPC UA specification.
<!--
== COM Components ==
== COM Components ==
== User Interface ==
== User Interface ==

Latest revision as of 16:28, 9 June 2025

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

Internal version number: 5.83

Key changes:


Technology

  • OPC UA Client-Server parts are now based on OPC Foundation UA-.NETStandard 1.5.376.213.
  • The OpcLabs.MqttNet communication package has been upgraded from MQTTnet and MQTTnet.Extensions.ManagedClient version 4.3.3.952 to 4.3.7.1207.

Packaging

  • Separated low-level OpcLabs.Core and OpcLabs.Core.Forms NuGet packages for reuse. This change is largely invisible to the developer; you keep referencing the same high-level NuGet packages as before, and the new packages get automatically referenced transitively.

Component Improvements

OPC UA PubSub

  • The custom connection property "0:MqttTopicPrefix" is interpreted as the <Prefix> part of the topic convention.
  • More relaxed decoding of JSON messages, allowing to process messages from publishers not fully conforming with the OPC UA specification.