SectionConfig 2.3.0
See the version list below for details.
dotnet add package SectionConfig --version 2.3.0
NuGet\Install-Package SectionConfig -Version 2.3.0
<PackageReference Include="SectionConfig" Version="2.3.0" />
paket add SectionConfig --version 2.3.0
#r "nuget: SectionConfig, 2.3.0"
// Install SectionConfig as a Cake Addin #addin nuget:?package=SectionConfig&version=2.3.0 // Install SectionConfig as a Cake Tool #tool nuget:?package=SectionConfig&version=2.3.0
SectionConfig
A .NET library which allows you to load plain-text configuration files. This is intended to replace ConfigTextFile.
Elements
There are five different elements: Keys, Sections, Values, Value Lists, and Comments. Sections, Values, and Value Lists all have a Key. Everything is a string. This config file format does not mandate any kind of data types that are required to be used; that is up to the application parsing the file. "Newline" is any of: a Line Feed, a Carriage Return, or Carriage Return followed by Line Feed.
Key
A Key is used to refer to the following element. This is either a section, value, or value list. Keys can't contain any of # : { } or newline characters, but they can contain spaces. Leading or trailing whitespace is ignored. A Key has to be unique within its section. The path of something is composed of every key of each parent section, followed by the key referring to the element. Each key is separated by a colon (:).
Values
A Key followed by a colon (:) and then some text is a Key/Value. If the value is on the same line, it's a single-line value. Leading or trailing whitespace is ignored. If there is no text after the colon, then it's interpreted as either an empty string, or a multiline value. If there text starts indented on the next line, it's a multiline value. The multiline value ends when the indentation is no longer present. To be precise: The 1st line defines the indentation to look for. Once that indentation is not found, the multi-line value ends. The resultant string will not end with a Linefeed or Carriage return. If the value is quoted ('single' or "double"), then it is literal; everything inside the quotes is taken exactly as is, including any whitespace. The only exception is the quote character used to quote the string; doubling it will produce a single quote character.
Sections
A Key followed by an open brace ({) opens a section. The Key becomes the name of that section. The section is closed with a close brace (}) Sections can contain any elements; more Sections, Key/Values, or Key/Value lists.
Value List
A Key followed by a colon (:) and then an open brace ({) is a Key/Value List. The Value List is closed with a close brace (}). Each string on a new line is a Value within that List. Values within the List can be quoted, which follow the same rules as a normal quoted Value (i.e. everything inside is taken literally)
Comments
A Comment is a number sign (#), followed by text. They must be the first thing on the line (besides whitespace).
Indentation
It's recommended to indent by 1 more level when you open a section or a value list. Tabs or spaces, whatever you prefer, just be consistent. The only time when indentation is significant is a multiline value. A multiline value is denoted by a Key on one line, and the next line being more indented than the Key was. "More indented" meaning the next line starts with the same indentation that the Key did, and has more indentation beyond that.
Examples
# A single value
Key: Value
# A single value, in quotes
Key: "Value"
Key: 'Value'
# Escaping quotes
Key: "To escape quotes, ""double"" them. 'Single' quotes are fine in here."
Key: 'You can''t use single quotes in here without doubling them, but "double" is fine!'
# Quotes in the middle of an unquoted value are fine
Key: This doesn't need to be quoted
Key: Nor "does" this
# You need quotes to include leading/trailing whitespace
Key: " Value with whitespace "
# You don't need to use quotes to denote an empty value, although you can if you want.
# All 3 of these are equivalent.
Key1:
Key2: ""
Key3: ''
# A single value spanning multiple lines. The indentation on the 1st and 3rd lines are not part of the string, but the extra indentation (3 extra spaces) on the 2nd line is part of the string.
Key:
This value
spans many lines
and doesn't include the indentation
# The indentation determines if text is a multiline value or an empty value.
# Not Empty is not more indented than Empty, so it's not the value of Empty:. It is a separate key.
# Because "The Value:" is indented more than "Not Empty:", it's considered the value with the key "Not Empty"
Empty:
Not Empty:
The Value:
# Quoted values, even if they start on the next line, are still literal. So this value will include the 3 spaces of indentation on the 3rd and 4th lines.
Key:
"This value
Spans many lines
But it DOES include the indentation"
# A value list is done like this. This has 3 values, "one", "two", and "three".
Key: {
one
two
three
}
# You can have quoted values in a value list as well, but note that they are completely literal.
Key: {
"this is just
one value"
"this is a separate value"
'also another value'
}
# Comments can be inside the value list as well
Key: {
one
# This is just a comment, not a value
two
three
}
# You can have blank lines within a list as well.
# If you want empty strings within a list, you must quote them.
# This list has 4 values: "one", "two", "three", and "" (empty string).
Key: {
one
two
three
""
}
# If you have quoted values, you don't need to separate them with newlines
Key: {"Compact list" "Each is a separate value" "Separated by just a space"}
# A section with a nested section. Sections can contain anything. The full path of something is each key, separated by a colon (:). The full paths of each of the elements below are commented.
# Path is "Example Section"
Example Section {
# Path is "Example Section:Key"
Key: Value
# Path is "Example Section:Nested Section"
Nested Section {
# Path is "Example Section:Nested Section:Key"
Key: {
Value 1
Value 2
Value 3
}
}
Another Section {
# Path is "Example Section:Another Section:Key"
Key: Value
}
}
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net5.0 was computed. net5.0-windows was computed. net6.0 is compatible. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 is compatible. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
.NET Core | netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
.NET Standard | netstandard2.0 is compatible. netstandard2.1 was computed. |
.NET Framework | net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
MonoAndroid | monoandroid was computed. |
MonoMac | monomac was computed. |
MonoTouch | monotouch was computed. |
Tizen | tizen40 was computed. tizen60 was computed. |
Xamarin.iOS | xamarinios was computed. |
Xamarin.Mac | xamarinmac was computed. |
Xamarin.TVOS | xamarintvos was computed. |
Xamarin.WatchOS | xamarinwatchos was computed. |
-
.NETStandard 2.0
- System.Memory (>= 4.5.4)
-
net6.0
- No dependencies.
-
net7.0
- No dependencies.
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|---|---|
3.0.0 | 109 | 2/4/2024 |
2.3.0 | 252 | 2/27/2023 |
2.2.0 | 215 | 2/27/2023 |
2.1.0 | 225 | 2/26/2023 |
2.0.0 | 215 | 2/26/2023 |
1.1.0 | 225 | 2/23/2023 |
1.0.0 | 406 | 5/28/2022 |
0.7.0 | 441 | 4/15/2022 |
0.6.0 | 424 | 4/8/2022 |
0.5.0 | 422 | 3/22/2022 |
0.4.0 | 243 | 12/30/2021 |
0.3.0 | 274 | 12/5/2021 |
0.2.0 | 275 | 11/22/2021 |
0.1.0 | 332 | 10/26/2021 |
- Fixed CfgStreamReader not working correctly for some TextReaders which do not completely fill the buffer before returning. Now, it only considers a zero-byte read to be the final block of the stream.
- CfgBufferHelper added to take care of buffering for the caller. CfgLoader.ReadAllBuffered moved to this struct.
- CfgBufferReader has a helper method to suggest a buffer of a new size.