Using default namespace with System.Xml.Linq.XAttribute explained. #44501
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.
Summary
The current documentation on "How to create a document with namespaces in C# (LINQ to XML)" doesn't explain how to handle the creation of new
XAttribute
objects that are supposed to have the enclosingXElement
's default namespace applied, e.g.:Without documentation, there are two options that might be hypothetically applicable for creating the correct XML with LINQ to XML in C#:
This pull request amends one of the examples by including information on how to create
XAttribute
objects applying to a default namespace.Fixes #44499
and dotnet/runtime#111703
Internal previews