The Core code to install as a NuGet package for all of my studio Solutions. Anyone who may be reading this 👀 is free to do the same. This package is based on a project file that supports multi-targeting, declaring support for net6.0.
NuGet package 📦: SonghayCore
documentation 📚: SonghayCore API
coverlet test coverage 🔬☔: [report]
The dominant theme in version 6.0 is about adopting .NET 6.0. The GitHub project for this release has the most documented details. Many version 6.0 changes are breaking changes.
Notable changes:
- Issue #131 was about removing direct support for WPF and any members marked obsolete in previous releases.
- Issue #135 was about separating Newtonsoft JSON routines from the Core.
- Issue #137 was about recognizing the new nullability features of .NET.
- Issue #140 was about finally adding coverlet code coverage.
This Core is exclusively concerned with tracing. 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
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:
-
IConfigurationBuilderExtensions— defines shared routines for application configuration building under .NET Standard. -
HttpRequestMessageExtensions— defines shared routines for HTTP access under .NET Standard with a lazy-loadedHttpClient. Routines for Azure Blob Storage are included here. -
HttpWebRequestExtensions— defines shared routines for HTTP access for the legacy .NET Framework. -
TraceSourceExtensions— defines shared routines forTraceSource-based logging, using work by Zijian Huang.
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
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
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
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
Core reusable, opinionated Newtonsoft concerns for my C# projects.
GitHub repo: https://github.com/BryanWilhite/SonghayCore.Newtonsoft
NuGet package 📦: SonghayCore.Newtonsoft
graph BT
netstandard2[.NET Standard 2.0]
net6[.NET 6.0]
1[`SonghayCore`]
2[`SonghayCore.Newtonsoft`]
net6-->1
netstandard2-->2
2-..->|optional addition|1
1-->3[`SonghayCore.xUnit`]
1-->4[`Songhay.DataAccess`]
1-->5[`Songhay.Feeds`]
1-->6[`Songhay.Publications`]
1-->7[`Songhay.Social`]