All ASP.NET developers expect to get these things “for free” and, finally, Microsoft is basically letting all .NET developers get these things for free. This Core recognizes the .NET Generic Host, stating with the DefaultHostedService class (see Songhay.Extensions below for more details).

Songhay.Diagnostics

This Core is concerned with tracing as well as logging. Logging concerns should be logically above this Core. TraceSources and TraceSourceExtensions define how tracing should be implemented with a bias toward using all source levels. When tracing is not configured for this Core then it will be ignored without throwing exceptions.

For a review of the organizational difference between tracing and logging, see “Tracing vs Logging vs Monitoring: What’s the Difference?” by Chrissy Kidd.

Documentation 📚: Songhay.Diagnostics

Songhay.Extensions

The Songhay System uses imperative C# code with a view to make it more functional in an effort to control complexity and enhance maintainability.

The preference for extension methods encourages stateless, reusable routines (many of them are “pure” functions).

Notable extensions:

• IConfigurationExtensions — defines shared routines based on conventions around the .NET Generic Host [📖 docs].

• IConfigurationBuilderExtensions — defines shared routines for application configuration building under .NET Standard.

• ILoggerExtensions — defines shared routines based on conventions around the .NET Generic Host [📖 docs].

• HttpRequestMessageExtensions — defines shared routines for HTTP access under .NET Standard with a lazy-loaded HttpClient. Routines for Azure Blob Storage are included here.

• HttpWebRequestExtensions — defines shared routines for HTTP access for the legacy .NET Framework.

There is support for URI templates (to be used with RestApiMetadata) in the form of extension methods, running on top of Tavis.UriTemplates.

Documentation 📚: Songhay.Extensions

Songhay.Models

The Core models of the Songhay System define types for MIME, XHTML, OPML, REST, the Repository, the Display Item (for WPF and other MVVM solutions), etc.

The Core models are “anemic” by design (there are very few abstract classes)—any logic would be found first in an Extension Method.

Notable models:

• DisplayItemModel — defines the conventional way to display data.

• MenuDisplayItemModel — defines the conventional way to display nested/grouped data.

• RestApiMetadata — defines conventional REST API metadata.

Documentation 📚: Songhay.Models

Songhay.Xml

The “core” of the Core is concern for XML. The Songhay System started out as utilities around XPathDocument and grew into LINQ for XML—over XDocument.

Documentation 📚: Songhay.Xml

satellite packages

SonghayCore.xUnit

Defines reusable class definitions for xUnit. Featured is the ProjectFileDataAttribute, allowing test data files to be loaded from a relative path.

NuGet package 📦: SonghayCore.xUnit

Documentation 📚: Songhay.Tests

SonghayCore.Newtonsoft

Core reusable, opinionated Newtonsoft concerns for my C# projects.

GitHub repo: https://github.com/BryanWilhite/SonghayCore.Newtonsoft

NuGet package 📦: SonghayCore.Newtonsoft

Studio packages dependent on SonghayCore

@BryanWilhite