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.
ExtendedXmlSerializer.Legacy
See original GitHub issueSo I am looking at the Configuration API now. I think you mentioned you did this, but the Legacy configuration was moved from legacy into v2 root.
The point of Legacy was to have it there in case people wanted to migrate their XML from v1 to v2.
But now I am thinking, maybe we should have an ExtendedXmlSerializer.Legacy nuget for this.
So we can take the Legacy out, and put it in this new package, along with tests. It would help make it less confusing? What do you think?
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (9 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
I see where the confusion is…
ExtendedXmlSerializeris public still. I was going to make it internal for #70, along with all the other classes for this task.Ok. great!