Request for .NET 6 or Higher Compatibility for Enhanced Cross-Platform Support #19
Replies: 4 comments 10 replies
-
|
I mainly stay at .Net framework, because .Net 6 isn't supported in Visual Studio 2019. And my final target is a C/C++ implementation to get a dll for use in any applications. |
Beta Was this translation helpful? Give feedback.
-
|
@thomas-v2, replacing openssl with a .net solution would greatly increase the value of the library and make a lot of .net developers very happy. |
Beta Was this translation helpful? Give feedback.
-
|
BouncyCastle seems to have almost no documentation, if you click on the link to the Api documentation, you get to a directory to download the binaries. When I've started the project, I didn't found any useful library. If I remember correctly, there is a native .Net implemenation of OpenSSL, but it lacks the BIO methods, which I need to pack the data into the IsoOnTCP payload. Most libraries support TLS only directly on the TCP layer. |
Beta Was this translation helpful? Give feedback.
-
|
Agreed. Not sure what the situation is with the current BouncyCastle doco. I don't recall it being quite as bad as it currently appears. |
Beta Was this translation helpful? Give feedback.
-
|
Ok, there are at least some examples to start with. I can't complain about the docs, they are similar to what I'm doing here. But for me personally, it's essential to have the opportunity to dump the session keys, to get the possibility to debug all in Wireshark if anything goes wrong or Siemens adds some new "features". |
Beta Was this translation helpful? Give feedback.
-
|
There's a closed issue with an example of how to get the session keys under bouncycastle tls |
Beta Was this translation helpful? Give feedback.
-
|
I would think potentially migrating the code to be .NET Standard 2.0 based might then suit both worlds. .NET Standard allows for the library to be used under the following .NET Framework versions: 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8, 4.8.1 Any objections if I were to look to make some PRs in this direction? |
Beta Was this translation helpful? Give feedback.
-
|
If a .Net Standard 2.0 library would work with .Net framework and .Net Core, then I think this would be the best solution. I'm only familiar with .Net Framework, so I don't know how many codechanges need to be made to switch to .Net Standard. |
Beta Was this translation helpful? Give feedback.
-
|
Hello everyone,
I have it compiled on ARM64 and .NET8.
The binaries are running on a docker container of .NET 8 on an YOCTO Machine.
I agree, it was a bit tricky to implement a suitable SSL Library, but it works right now.
I'm using the project to create a Siemens to Rockwell Data Exchanger as prototype.
Do you have further plans to maintain the code, I would highly appreciate it.
Best regards,
Mike
…________________________________
From: thomas-v2 ***@***.***>
Sent: Wednesday, January 8, 2025 18:24
To: thomas-v2/S7CommPlusDriver ***@***.***>
Cc: Mike SINGE ***@***.***>; Manual ***@***.***>
Subject: Re: [thomas-v2/S7CommPlusDriver] Request for .NET 6 or Higher Compatibility for Enhanced Cross-Platform Support (Discussion #19)
I think I've looked at this too, if I remember correctly it does not support TLS 1.3, or there is any other dependancy on the operating system to get it working with TLS1.3, which I didn't want to have because I needed to support older operation systems and also 32 bit machines. I'd prefer to rewrite the complete driver in Rust and get a dll with a C compatible Api, this is much more flexible.
—
Reply to this email directly, view it on GitHub<#19 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AH5AIGBRXBYNMGIMX6QGEET2JVNOHAVCNFSM6AAAAABUZ7TLO6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNZXGY2DGNA>.
You are receiving this because you are subscribed to this thread.
|
Beta Was this translation helpful? Give feedback.
-
|
@MikeSinge how did you go about handling the SSL aspect? Do you have a similar EthernetIP/CIP 'driver' to do the Rockwell side of things? |
Beta Was this translation helpful? Give feedback.
-
|
Hello Bevan,
was on my way back from winter vacation, sorry for the delay.
If so, what license do you have for it... any chance it's open source?
I'm using for the Exchanger this lib, it's working perfectly fine:
libplctag/libplctag: This C library provides a portable and simple API for accessing Allen-Bradley and Modbus PLC data over Ethernet.<https://github.com/libplctag/libplctag>
[https://opengraph.githubassets.com/c4a22b27e988db2a01add3e3ecef8847706fd7ffa6a8bcb7dfee80eef006d6ae/libplctag/libplctag]<https://github.com/libplctag/libplctag>
libplctag/libplctag: This C library provides a portable and simple API for accessing Allen-Bradley and Modbus PLC data over Ethernet. - GitHub<https://github.com/libplctag/libplctag>
libplctag is an open source C library for Linux, Windows and macOS using EtherNet/IP or Modbus TCP to read and write tags in PLCs. The library has been in production since early 2012 and is used by multiple organizations for many tasks including controlling radio telescopes, large and precision manufacturing, controlling fitness equipment, food handling and many, many more.
github.com
Because this topic doesn't have anything to do with S7CommDriver, you can reply directly to my email address:
***@***.***
…________________________________
From: Bevan Weiss ***@***.***>
Sent: Friday, January 10, 2025 06:30
To: thomas-v2/S7CommPlusDriver ***@***.***>
Cc: Mike SINGE ***@***.***>; Mention ***@***.***>
Subject: Re: [thomas-v2/S7CommPlusDriver] Request for .NET 6 or Higher Compatibility for Enhanced Cross-Platform Support (Discussion #19)
@MikeSinge<https://github.com/MikeSinge> how did you go about handling the SSL aspect?
I think the use of SSLStream would be the nicest way, since it would be supported under .NET Standard 2.0 (i.e. it could work for .NET Framework and .NET Core).
Do you have a similar EthernetIP/CIP 'driver' to do the Rockwell side of things?
If so, what license do you have for it... any chance it's open source?
—
Reply to this email directly, view it on GitHub<#19 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AH5AIGBRSFVIDVMINRJHHQT2J5LIDAVCNFSM6AAAAABUZ7TLO6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNZZGM4TKOI>.
You are receiving this because you were mentioned.
|
Beta Was this translation helpful? Give feedback.
-
I hope this message finds you well. I am reaching out to discuss the potential of upgrading the S7CommPlusDriver to be compatible with .NET 6 or higher versions. This enhancement would significantly broaden the library's usability, especially in terms of cross-platform capabilities.
As you're aware, .NET 6 brings forward many improvements, including increased performance, reduced resource consumption, and most importantly, robust cross-platform support. This aligns well with the growing need for applications that seamlessly operate across different environments.
Implementing support for .NET 6 or later versions would not only future-proof the library but also expand its accessibility to a wider developer community, who are increasingly relying on .NET for building versatile applications. This upgrade could potentially open up new avenues for collaboration and usage, especially in scenarios where cross-platform compatibility is crucial.
I understand that such an upgrade requires time and resources, and I appreciate the effort the team puts into maintaining and enhancing this project. If there's anything I can assist with, please let me know. I, along with many in the community, eagerly look forward to the possibility of this upgrade and the new opportunities it would bring.
Thank you for your consideration and the excellent work you do with [Library/Project Name]. I am excited about the prospect of its continued evolution and the impact it could have on the .NET community.
Best regards,
Beta Was this translation helpful? Give feedback.
All reactions