[dotnet-svcutil] defer known types import to resolve IsReference inheritance issue #5810
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #5769: The DataContract IsReference property was incorrectly set to false for some derived types when known types and inheritance were involved. This led to a mismatch between the imported DataContract type and the referenced type, which caused issues when trying to reuse the referenced types.
Root cause: ImportKnownTypes(typeName) was called immediately after importing each type, which could import derived types as known types before their base types were fully processed, causing inheritance-based IsReference propagation to fail.
Solution: Implement deferred known types import strategy:
This ensures that inheritance-based property propagation works correctly by processing known types only after the complete type hierarchy is established.