JJ.Framework.Xml 1.5.6877.41334

XmlToObjectConverter converts an XmlDocument or string to an object graph. The way to map XML to classes is easier than the classic ways in .NET. XmlHelper allows you to access XML in a null-safe and multiplicity-safe way. It uses XmlDocument as the underlying .NET API.

Install-Package JJ.Framework.Xml -Version 1.5.6877.41334
dotnet add package JJ.Framework.Xml --version 1.5.6877.41334
<PackageReference Include="JJ.Framework.Xml" Version="1.5.6877.41334" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add JJ.Framework.Xml --version 1.5.6877.41334
The NuGet Team does not provide support for this client. Please contact its maintainers for support.

JJ.Framework.Xml

Helpers for working with XML.

XmlHelper

A class that gives access to XML. It does so in a null-safe and multiplicity-safe way. It uses XmlDocument as the underlying .NET API.

Members:

  • SelectNode / TrySelectNode
    • Select a node by XPath.
  • GetElement / TryGetElement / GetElements
    • Get child elements by name.
  • GetAttribute / TryGetAttribute
    • Get attributes by name.
  • GetAttributeValue / TryGetAttributeValue / SetAttributeValue
    • Get and set attribute values.

Remarks:

  • The Try variations can return null.
  • The non-Try variations cannot return null, but when nothing is found, will throw a clear exception instead.
  • The singular (non-plural) variations will throw a clear exception, when the item is not unique.

XmlToObjectConverter

Converts an XmlDocument or string to an object graph. The way to map to classes is easier than the classic ways in .NET. The idea was to make XML mapping intuitive and clean. (Also: At the time on certain platforms standard XML serialization was not available or not be the best option.)

Elements

By default properties are mapped to XML elements.

C#:

public int MyElement { get; set; }

XML:

<myElement>3</myElement>

Attributes

To map to XML attributes, mark a property with the XmlAttribute attribute.

C#:

[XmlAttribute]
public int MyAttribute { get; set; }

XML:

myAttribute="3"

Collections

If a property is a collection type, a parent XML element is expected, and a child element for each position in the array.

C#:

public int[] MyArray { get; set; }

XML:

<myArray>
  <int32>2</int32>
  <int32>3</int32>
  <int32>5</int32>
</myArray>

That single collection property maps to both this parent element and the child elements.

The supported collection types are Array types, List<T>, IList<T>, ICollection<T> and IEnumerable<T>.

Composite Types

You can easily work with composite types.

XML:

<myRoot>
  <myObject1 value="3" />
  <myObject2>
    <myArray>
      <item name="Name1" value="1" />
      <item name="Name2" value="2" >
        <childItem name="Child" value="3" />
      </item>
    </myArray>
  </myObject2>
</myRoot>

C#:

class MyRoot
{
    public MyClass MyObject1 { get; set; }
    public MyClass MyObject2 { get; set; }
}

class MyClass
{
    [XmlAttribute]
    public string Name { get; set; }

    [XmlAttribute]
    public int? Value { get; set; }

    [XmlArrayItem("item")]
    public MyClass[] MyArray { get; set; }

    public MyClass ChildItem { get; set; }
}

The composite types in the object structure must have parameterless constructors.

C#:

class MyClass
{
    // Having this constructor with a parameter causes an exception.
    public MyClass(int myConstructorParameter) { }
}

Standard Naming

By default the names in the XML are the camel-case version of the property names.

C#:

public int MyElement { get; set; }

XML:

<myElement>3</myElement>
Standard Naming for Collections

For XML array items, however, it is not the property name, but the camel case version of collection property's item type.

C#:

public int[] MyArray { get; set; }

XML:

<myArray>
  <int32>2</int32>
  <int32>3</int32>
  <int32>5</int32>
</myArray>

Custom Naming

To diverge from the standard naming , you can specify the node name explicitly by using the following .NET attributes on the properties: XmlElement, XmlAttribute, XmlArray and XmlArrayItem.

Custom Naming for Elements

C#:

[XmlElement("Elm")]
public int MyElement { get; set; }

XML:

<Elm>3</Elm>
Custom Naming for Attributes

C#:

[XmlAttribute("Attr")]
public int MyAttribute { get; set; }

XML:

Attr="3"
Custom Naming for Arrays

C#:

[XmlArray("Arr")]
[XmlArrayItem("Item")]
public int[] MyArray { get; set; }

XML:

<Arr>
  <Item>2</Item>
  <Item>3</Item>
  <Item>5</Item>
</Arr>

Nullability

Effort was made to make nullability as intuitive as possible.

Nullability for Reference Types

Reference types are always optional.

C#:

class MyRoot
{
	// Can be null
	public MyClass MyObject { get; set; }
}

XML:

<myRoot>
  <!-- No myObject element here, so the MyObject property in C# will be null. -->
</myRoot>
Nullability for Value Types

Value types are optional, only if they are nullable.

C#:

class MyRoot
{
	// The '?' makes it OK to leave out the XML element.
	public int? MyElement { get; set; }
}

XML:

<myRoot>
  <!-- myElement van be left out. -->
  <!-- Then the MyElement property in the C# code will be null. -->
</myRoot>

C#:

class MyRoot
{
	// Without the '?' the XML element is required.
	public int MyElement { get; set; }
}

XML:

<myRoot>
  <!-- myElement is required, otherwise you will get an exception. -->
  <myElement>3</myElement>
</myRoot>
Nullability for Collections

Collection types are always optional.

C#:

class MyRoot
{
	public int[] MyArray { get; set; }
}

If the parent element is missing from the XML, the collection will be null.

XML:

<myRoot>
  <!-- myArray can be left out, -->
  <!-- but then MyArray in the C# code will be null. -->
</myRoot>

If only the parent element is present, an empty collection will be assigned.

XML:

<myRoot>
  <!-- MyArray in the C# code will not be null, but an empty collection. -->
  <myArray />
</myRoot>

Value Types

Recognized values are the .NET primitive types: Boolean, Char, Byte, IntPtr, UIntPtr, the numeric types, their signed and unsigned variations and String, Guid, DateTime, TimeSpan and Enum types.

Error Messages

Effort was put into making the exception messages clear and accurate if there are structure mismatches.

Performance

In short: performance is untested. I know it is a thing that people want to prove they have the fastest serializer. I really just wanted to map XML more easily. Other components I made depend on it.

JJ.Framework.Xml

Helpers for working with XML.

XmlHelper

A class that gives access to XML. It does so in a null-safe and multiplicity-safe way. It uses XmlDocument as the underlying .NET API.

Members:

  • SelectNode / TrySelectNode
    • Select a node by XPath.
  • GetElement / TryGetElement / GetElements
    • Get child elements by name.
  • GetAttribute / TryGetAttribute
    • Get attributes by name.
  • GetAttributeValue / TryGetAttributeValue / SetAttributeValue
    • Get and set attribute values.

Remarks:

  • The Try variations can return null.
  • The non-Try variations cannot return null, but when nothing is found, will throw a clear exception instead.
  • The singular (non-plural) variations will throw a clear exception, when the item is not unique.

XmlToObjectConverter

Converts an XmlDocument or string to an object graph. The way to map to classes is easier than the classic ways in .NET. The idea was to make XML mapping intuitive and clean. (Also: At the time on certain platforms standard XML serialization was not available or not be the best option.)

Elements

By default properties are mapped to XML elements.

C#:

public int MyElement { get; set; }

XML:

<myElement>3</myElement>

Attributes

To map to XML attributes, mark a property with the XmlAttribute attribute.

C#:

[XmlAttribute]
public int MyAttribute { get; set; }

XML:

myAttribute="3"

Collections

If a property is a collection type, a parent XML element is expected, and a child element for each position in the array.

C#:

public int[] MyArray { get; set; }

XML:

<myArray>
  <int32>2</int32>
  <int32>3</int32>
  <int32>5</int32>
</myArray>

That single collection property maps to both this parent element and the child elements.

The supported collection types are Array types, List<T>, IList<T>, ICollection<T> and IEnumerable<T>.

Composite Types

You can easily work with composite types.

XML:

<myRoot>
  <myObject1 value="3" />
  <myObject2>
    <myArray>
      <item name="Name1" value="1" />
      <item name="Name2" value="2" >
        <childItem name="Child" value="3" />
      </item>
    </myArray>
  </myObject2>
</myRoot>

C#:

class MyRoot
{
    public MyClass MyObject1 { get; set; }
    public MyClass MyObject2 { get; set; }
}

class MyClass
{
    [XmlAttribute]
    public string Name { get; set; }

    [XmlAttribute]
    public int? Value { get; set; }

    [XmlArrayItem("item")]
    public MyClass[] MyArray { get; set; }

    public MyClass ChildItem { get; set; }
}

The composite types in the object structure must have parameterless constructors.

C#:

class MyClass
{
    // Having this constructor with a parameter causes an exception.
    public MyClass(int myConstructorParameter) { }
}

Standard Naming

By default the names in the XML are the camel-case version of the property names.

C#:

public int MyElement { get; set; }

XML:

<myElement>3</myElement>
Standard Naming for Collections

For XML array items, however, it is not the property name, but the camel case version of collection property's item type.

C#:

public int[] MyArray { get; set; }

XML:

<myArray>
  <int32>2</int32>
  <int32>3</int32>
  <int32>5</int32>
</myArray>

Custom Naming

To diverge from the standard naming , you can specify the node name explicitly by using the following .NET attributes on the properties: XmlElement, XmlAttribute, XmlArray and XmlArrayItem.

Custom Naming for Elements

C#:

[XmlElement("Elm")]
public int MyElement { get; set; }

XML:

<Elm>3</Elm>
Custom Naming for Attributes

C#:

[XmlAttribute("Attr")]
public int MyAttribute { get; set; }

XML:

Attr="3"
Custom Naming for Arrays

C#:

[XmlArray("Arr")]
[XmlArrayItem("Item")]
public int[] MyArray { get; set; }

XML:

<Arr>
  <Item>2</Item>
  <Item>3</Item>
  <Item>5</Item>
</Arr>

Nullability

Effort was made to make nullability as intuitive as possible.

Nullability for Reference Types

Reference types are always optional.

C#:

class MyRoot
{
	// Can be null
	public MyClass MyObject { get; set; }
}

XML:

<myRoot>
  <!-- No myObject element here, so the MyObject property in C# will be null. -->
</myRoot>
Nullability for Value Types

Value types are optional, only if they are nullable.

C#:

class MyRoot
{
	// The '?' makes it OK to leave out the XML element.
	public int? MyElement { get; set; }
}

XML:

<myRoot>
  <!-- myElement van be left out. -->
  <!-- Then the MyElement property in the C# code will be null. -->
</myRoot>

C#:

class MyRoot
{
	// Without the '?' the XML element is required.
	public int MyElement { get; set; }
}

XML:

<myRoot>
  <!-- myElement is required, otherwise you will get an exception. -->
  <myElement>3</myElement>
</myRoot>
Nullability for Collections

Collection types are always optional.

C#:

class MyRoot
{
	public int[] MyArray { get; set; }
}

If the parent element is missing from the XML, the collection will be null.

XML:

<myRoot>
  <!-- myArray can be left out, -->
  <!-- but then MyArray in the C# code will be null. -->
</myRoot>

If only the parent element is present, an empty collection will be assigned.

XML:

<myRoot>
  <!-- MyArray in the C# code will not be null, but an empty collection. -->
  <myArray />
</myRoot>

Value Types

Recognized values are the .NET primitive types: Boolean, Char, Byte, IntPtr, UIntPtr, the numeric types, their signed and unsigned variations and String, Guid, DateTime, TimeSpan and Enum types.

Error Messages

Effort was put into making the exception messages clear and accurate if there are structure mismatches.

Performance

In short: performance is untested. I know it is a thing that people want to prove they have the fastest serializer. I really just wanted to map XML more easily. Other components I made depend on it.

Version History

Version Downloads Last updated
1.5.6877.41334 375 10/31/2018
1.4.6869.42104 110 10/22/2018
1.4.6868.31772 99 10/21/2018
1.4.6867.38923 172 10/20/2018
1.4.6867.38409 97 10/20/2018