Migrating PLC4Net from 0.13.1 to 1.0.0

This page covers the C# (.NET) binding.

PLC4Net is abandoned. It is not ready for usage, it has no driver implementations, and no work went into it for 1.0.0 beyond keeping it compiling and refreshing the generated protocol data.

If you are looking for a way to talk to a PLC from .NET today, the practical options are the PLC4X Server or the OPC UA Server - both let a non-Java application reach any PLC that PLC4X can reach, over a protocol that has good .NET client libraries.

Short version

There is nothing to migrate. The plc4net API and SPI are the same as in 0.13.1. Nothing was added, renamed or removed.

What did change

Only generated data, which affects nobody’s source code:

  • The bundled KNX manufacturer data and the BACnet and KNX vendor IDs were refreshed for broader device recognition. This is the same refresh every binding got.

  • The generated BACnet, OPC UA and KNX types were regenerated against the current mspec definitions.

Building

The PLC4X build migrated to Apache Maven 4. This only concerns you if you build plc4net from the PLC4X source tree with -Pwith-dotnet.

Everything else

The changes described on the overview page - the array notation, the connection-string vocabulary, the security defaults - are changes to drivers, and plc4net has none. They become relevant only if the .NET binding is ever picked up again.