Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Question about not using ConfigurationContainer
See original GitHub issueI have just started working on a project that has ExtendedXmlSerializer included. The file version of the .dll is 1.5.0.0 and it has a date of 08/17/2017 (could have been copied with date changing methods).
The serialization code is simply (no references to ConfigurationContainer anywhere in the project)
ExtendedXmlSerializer serializer = new ExtendedXmlSerializer(); String message = serializer.Serialize(messageObject);
Are we receiving any benefit by using ExtendeXmlSerializer over built in XML Serialization classes. From reading the doc, it appears that most everything like circular references must be accounted for in the configuration of the ConfigurationContainer.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Paging @wojtpl2 😃
@SOHODeveloper Hi I’m going to close this issue right now. If you have more questions or if my answer is not enough for you, please let me know. Please feel free to re-open this issue or create a new one.