| Where | What |
|---|---|
| BlogSpot Ex-Pression | Texts (French, English) |
| GitHub | Repositories |
| NuGet | Packages |
| PowerShell Gallery | Modules |
| SoundCloud Ex-Pression | Tunes |
The .Net libraries names, and the namespaces they contain, are unconventional and do not follow the usual namings found in the framework because naming conventions in the framework evolved over time and are not always consistent across components.
For instance, System.Text.Json is about serialization, and System.Xml.Serialization is handling text data.
So instead of trying to follow rules that do not exist, that change over time or that depend on the team that created the components; I prefer being consistent and predictable so you just have the surprise once: on the first library you use.
A capability repository often produces two packages:
- the abstractions with interfaces and primitives (e.g. Scal.Serializing.Abstractions)
- the core implementation (e.g. Scal.Serializing)
Scal.Interpreting.Commands
Scal.Serializing
Scal.Serializing.Csv
Scal.Serializing.Ini
Scal.Serializing.Json
Scal.Serializing.Json.Schemas
Scal.Serializing.Xml
The MSBuild Sdk's project are named Scal.Sdk.xxx, see Scal.Sdk.