Closed blakecodes closed 3 years ago
Issue-Label Bot is automatically applying the label bug
to this issue, with a confidence of 0.52. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
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 List<T>
member definitions. As a more specific example, the Channel.Link
member from your provided model is of type List<string>
and that is throwing us for a loop.
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. 👍
GitHubA configurable and eXtensible Xml serializer for .NET. - ExtendedXmlSerializer/home
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
List<T>
member definitions. As a more specific example, theChannel.Link
member from your provided model is of typeList<string>
and that is throwing us for a loop.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. 👍
GitHubExtendedXmlSerializer/homeA configurable and eXtensible Xml serializer for .NET. - ExtendedXmlSerializer/home
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.
GitHubA configurable and eXtensible Xml serializer for .NET. - ExtendedXmlSerializer/home
FWIW marking this issue as helpwanted/won't fix
as it unfortunately falls outside of the allotted/due-diligence time I have per #383. I will leave it open for the community to take a look at for a while and then archive it if no one takes up the challenge.
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: