Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems with parsing probe with extensions #94

Open
SergiiGulyk opened this issue Feb 1, 2025 · 1 comment
Open

Problems with parsing probe with extensions #94

SergiiGulyk opened this issue Feb 1, 2025 · 1 comment
Assignees

Comments

@SergiiGulyk
Copy link
Contributor

Hi Patrick!

Long time since our last talk :)

We have got recently a new machine that has extensions not only in vocabulary of the probe (as in your Okuma example), but also in components.
Please see attached probe file.
<x:Wire> is the culprit of hanging when XmlReader tries to parse the document.
Actually, the parse hangs forever, and I am afraid it is a bug in .NET generated assembly, as it cannot skip unknown element correctly.

I really dislike that black magic of XmlSerializer and personally prefer an explicit approach you used with DeviceStreams.

Any ideas?

Best wishes,
Sergii Gulyk.

Probe-Sodick-VN600Q.txt

@PatrickRitchie
Copy link
Contributor

Yes, it needs to be rewritten to not use the XmlSerializer. I have ran into similar issues a few times. It should be possible to use source generation based on the SysML model to generate the majority of the code needed. I'll add this to the ToDo list.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

2 participants