SharpConfig Versions Save

• Added the Configuration.StringRepresentation property
• Fixed a redundant beginning empty line when saving a textual configuration
• Fixed the order of how sections are written
• Added missing documentation

• Added .NET Standard 2.0 support (issue #94)
• Added the ability to parse configurations without sections (issue #85)
• Added the ability to convert empty setting values to non-string types (issue #86)

• Added .NET Core support and removed assembly signing
• Added binaries for .NET Standard and Core
• New static Configuration property: OutputRawStringValues (thanks @maxotek !)

• Fixed parsing of backslashed comments inside and outside of quoted values (#72)
• Introduced usage of C# string interpolation and other new language features (#64) (thanks @MCCshreyas !)

Fixed issue #63.

Fixed issue #62.

Fixed issue #60.

SharpConfig.3.2.2.zip This is a hotfix release.

• Fixed a bug where array were saved inside quotes (issue #59). Example:

  • Expected output: {"0","1","2","Some String"}
  • Actual output: "{0,1,2,Some String}" This lead to potentially incorrect parsing of arrays and made quoted array values impossible.

• Fixed a bug where quoted strings would not preserve the quotes upon direct setting of array values (issue #59)

• Removed space between '=' to ensure compatibility with other applications
  • Example: settings are now saved as "mySetting=myValue" instead of "mySetting = myValue"
• Improved documentation
• Fixed a parsing bug/crash that occurred when pre-comments were disabled (Configuration.IgnorePreComments).
• Fixed inconsistent writing/reading of quoted string values (issue #56)
• The Setting.StringValueTrimmed property is now obsolete and will be removed with the next release
• Fixed binary (de)serialization of array values
• Added new properties to Setting:
  • RawValue
  • DecimalValue, DecimalValueArray
  • ByteValue, ByteValueArray
  • SByteValue, SByteValueArray
  • CharValue, CharValueArray (issue #58)
• Fixed a bug that occurred when trying to convert an out-of-sbyte-range integer to a byte

• Fixed a parsing issue regarding quoted array values (issue #53).
• Fixed Section.SetValuesTo() to handle array setting values (issue #54).
• Improved configuration parsing regarding section and setting names.
  • Section names may now contain any char, including '[' and ']'.
  • Setting names may now be quoted to include any char, including '='.
    • Example: "My Setting" = "My Value"
    • Or: "My\"=$%&Setting" = "My Value"
• Removed the Comment struct.
• Removed the Configuration.NumberFormat and Configuration.DateTimeFormat properties.
• Added Setting.IsEmpty property.
• Added (issue #55):
  • Configuration.Add(string sectionName)
  • Section.Add(string settingName)
  • Section.Add(string settingName, object settingValue)
• Added ParserException.Line property.
• Added Setting.StringValueTrimmed property.