Hi all, PLC4Net now includes S7 and Modbus drivers, along with the transports needed by those drivers. I have also tested basic read and write operations with physical S7 and Modbus devices.
I think it would be useful to establish a repeatable way to build, verify, and distribute PLC4Net packages, starting with the existing S7 and Modbus functionality. This would make it easier for .NET users to try PLC4Net and provide a foundation for adding more protocol drivers later. I would be happy to help with the preparation work, including checking package contents and dependencies, testing installation from a clean .NET project, and updating the package documentation. I would appreciate the community's thoughts on: - Would it make sense to include PLC4Net NuGet packages in an upcoming PLC4X release? - Does the project already have a NuGet.org account or organization that should be used? What package naming, versioning, and publishing process would the project prefer? - What would be the appropriate way to provide packages to the development community for testing, and are there other requirements we should address before publication? Best, TomNewChao
