...
- The runtime publishes server performance counters on a secured REST API endpoint. See Runtime REST API Reference.
- FxResourceMonitor records CPU and memory of every FrameworX runtime process on Windows. The diagnostic tool runs independently of the runtime, logs process starts and exits, and summarizes growth, high CPU and crashes in a report. See FxResourceMonitor Reference.
- The runtime REST API publishes an OpenAPI document and supports authenticated cross-origin browser calls. Login responses state when the session expires, and tag history returns stored values for tags in normalized historian tables. See Runtime REST API Reference.
- Runtime diagnostics and System Monitor values work on .NET 10 runtimes on Windows, Linux and macOS. The diagnostics file adds FrameworX process trends and TCP connections and is generated in about one second. See Runtime Diagnostics Reference.
- A runtime licensed from a remote license server tolerates outages of about 300 minutes. Runtimes with a local license behave as before.
- Opening a solution from an earlier version always saves a backup copy before the upgrade. Solution Center shows an Upgrade action for a solution whose upgrade prompt was declined. See Upgrading Solutions Reference.
- Operators see the license expiration warning only in the final week before expiration. Earlier notices and maintenance-plan expirations go to the server event log, and the warning shows the product name as its title.
- Clients connected through the Secure Gateway finish loading the solution. The service opens each listener on its own port. See SecureGateway Services Reference.
- Startup tools report unrecognized launch parameters and why a .NET 10 runtime component failed to launch. The launch failure reason is written to the Startup log when Save log is enabled for the profile. See Runtime Startup Reference.
- The Tatsoft.FrameworX PowerShell module is installed with the product. It imports on Windows PowerShell 5.1 and PowerShell 7. See Tatsoft.FrameworX PowerShell Module Reference.
- Designer, Solution Center and runtime clients reconnect after a lost server connection without a restart. The .NET Framework edition of the TWebServices gateway releases Tag Provider connection memory when a connection closes or times out.
- A forced write updates a tag's Previous Value and Timestamp, including when the value is unchanged. Digital tags raise an event on a Device read or normal write only when the value or quality changes, and store 0 or 1.
- On Linux and Docker, a Windows-target solution gets a clear message with the step that moves it to Multiplatform. On Linux and macOS, a runtime started from a terminal stops in order on Ctrl+C or when the terminal closes. See Linux Deployment Reference.
- Solution Center Start runs a solution as a Windows Service when it is configured as one. Administrators can remove the runtime Windows service from the command line, with clear status reporting.
- Module start problems are reported clearly as Cannot Start Module, and the runtime keeps running. Value updates on the client continue throughout.
- Historian, Dataset and Device modules keep normal operation through every online configuration change. The Module Information window updates as soon as the in-process Devices module stops or restarts.
- The continuous runtime trace file is a valid tab-delimited file. Trace output stays on when an unrecognized client changes trace settings, and Device Points mapped in two channels raise no repeated warnings.
- Saving a database connection, device node or tag provider at runtime keeps its base connection settings. Applies when the solution runs on an execution profile that overrides the connection.
- The built-in MQTT broker keeps running on .NET 10 solutions.
- A computer with teamed network adapters keeps its activated license across restarts.
- Reconnecting client stations receive the current tag values from the server. Tags keep their values, quality and timestamps through client reconnections and online configuration changes, so alarms and device writes follow real process changes. Applies when every Smart Client and Rich Client runs this release.
- FxResourceMonitor also runs on Linux and macOS with the .NET 10 runtime. It records machine and process CPU and memory, follows process starts and exits, and registers to start at boot as a systemd service or a launchd daemon.
- Setup on Windows 11 24H2 and later closes running .NET 10 FrameworX processes before it updates files. Upgrades restart the FxResourceMonitor startup task, and uninstalling removes it.
...
Good To Know Changes
These changes need no action. They are listed so you know what to expect on 10.1.6.
...