You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Introduction of a C#/.NET client for OpenSysML #1938
Hello, my collaborators and I wanted to start a discussion regarding the work that we are doing to add a .NET client to OpenSysML. The ongoing work can be found here: richetl#1
We have completed the bulk work of the client, bringing it up to parity with both the Java and Python clients. We are currently interating through all the checks in CONTRIBUTING.md as well as generally reviewing the overall corpus of C# code for efficiency, reuse, and architectural improvements.
As this is a large addition of code, we did not want to just file a pull request but rather start a conversation and understand what the willingness of the maintainers to accept a new client is. We can also break the work up into several different PRs if that would make the process flow more smoothly. Again, we are looking to discuss and understand before just throwing PRs y'all's way.
We have been developing this using the instructions in CONTRIBUTING.md and having AGENTS.md guide our usage of AI. We are currently building on top of this .NET client, so in addition to the test suite we have created, we are truly using it and improving it.
Ideally, if we can upstream this client, and then publish to nuget, the .NET client could be easy to integrate using standard .NET paradigms. Looking forward to the discussion and contributing.
Hello! Thank you for opening this issue. We are definitely willing to accept a new community contributed client! The only concerns that I would have are the overhead it might have in testing, so I will have to think about how to split everything up a bit better than how it currently is. As for the format, I did take a cursory look at the client and while it is quite significant, I would not mind a single PR and keeping everything together.
As for nuget, I have been working to get OpenSysML available via nuget. I had opened a request for Z3 packaging to be there, as that is an optional dependency of OpenSysML. I'll catch back up on that to make sure it's been accepted now and open the request for OpenSysML. I think having the .NET client makes sense and we can add it, I have no objections.
Activity
HuiJun commentedon Nov 4, 2026
Hello! Thank you for opening this issue. We are definitely willing to accept a new community contributed client! The only concerns that I would have are the overhead it might have in testing, so I will have to think about how to split everything up a bit better than how it currently is. As for the format, I did take a cursory look at the client and while it is quite significant, I would not mind a single PR and keeping everything together.
HuiJun commentedon Nov 4, 2026
As for nuget, I have been working to get OpenSysML available via nuget. I had opened a request for Z3 packaging to be there, as that is an optional dependency of OpenSysML. I'll catch back up on that to make sure it's been accepted now and open the request for OpenSysML. I think having the .NET client makes sense and we can add it, I have no objections.
richetl commentedon Nov 11, 2026
Opened #2147 to start working towards a merge
@kevinpallan