-
Notifications
You must be signed in to change notification settings - Fork 47
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
XmlElementAttribute
Does Not Have 100% Fidelity with Classic Serializer
#461
Comments
Issue-Label Bot is automatically applying the label Links: app homepage, dashboard and code for this bot. |
Branch issues/fix/i461 created! |
Thank you for writing in with this, @blakecodes. I took a look at this, and while we do have some basic support for classic serialization scenarios, there appears to be a problem here with how we're interpreting the ExtendedXmlSerializer works best when deserializing a document that was serialized by ExtendedXmlSerializer. You can read more behind this here from our wiki: https://github.com/ExtendedXmlSerializer/home/wiki/FAQs#systemxmlserializer-vs-extendedxmlserializer If you are adventurous enough, my recommendation would be to use XSLT and run the RSS document through it, producing the resulting document that ExtendedXmlSeializer would work better at deserializing. Otherwise, as per #383 since this falls outside of the primary use scenario I unfortunately will not have time to look into this further. However, if someone would like to submit a PR to address this I would be more than happy to collaborate towards a commit. 👍
|
Thanks @Mike-E-angelo, I'll take a look to see if I can create a fix for it. We've got a few use cases for a deserializer and this seems to be closest to what we want to use.
|
FWIW marking this issue as |
XmlElementAttribute
Support Does Not Have 100% Fidelity with Classic Serializer
XmlElementAttribute
Support Does Not Have 100% Fidelity with Classic SerializerXmlElementAttribute
Does Not Have 100% Fidelity with Classic Serializer
There hasn't been much activity here, so will be closing for now. If something does change please feel free to leave a comment here and we'll take it from there. 👍 |
I seem to be running into an issue deserializing from an XML HTTP GET response. Could someone provide some clarity on how I could resolve this?
Configuration:
var serializer = new ConfigurationContainer().EnableImplicitTyping(typeof(Rss)).Create();
Class:
XML Content:
The text was updated successfully, but these errors were encountered: