CoreLibrary

CoreLibrary is a modular collection of .NET utility libraries, helpers, and samples created to provide common functionality across applications and projects. It is organized into multiple smaller projects (packages) so you can pick only the components you need.

Key modules

• CoreLibrary.Base / CoreLibrary.Classes - foundational types, extensions, and base classes.
• CoreLibrary.Interfaces / CoreLibrary.Interfaces.* - interface definitions used across modules (logging, configuration, general helpers).
• CoreLibrary.Logging - logging abstractions and implementations, plus integrations such as CoreLibrary.Serilog and CoreLibrary.FileLogger.
• CoreLibrary.Files - file utilities.
• CoreLibrary.Threads - threading utilities and helpers.
• CoreLibrary.ForEach - helper utilities for collection iteration patterns.
• CoreLibrary.TypedBackgroundWorker - background worker with typed messages and tests.
• CoreLibrary.PassingProperties - utilities for passing properties/state between components.

Supported target frameworks

This repository contains projects targeting multiple frameworks to maximize compatibility, including:

• .NET Standard 2.0 / 2.1
• .NET Framework (3.5 up to 4.8.1)
• .NET 5 / .NET 6 / .NET 7 (where applicable)

Individual project .csproj files specify their exact target frameworks.

Getting started

• Clone the repository and open the solution in Visual Studio.
• Build the solution to restore NuGet packages and compile all projects.

Build from command line

Most SDK-style projects can be built with the .NET CLI:

dotnet build <project-or-solution-file>

Note: Some legacy projects target older .NET Framework TFMs and require Visual Studio/MSBuild to build successfully.

Testing

Unit tests are available in the CoreLibraryTest project(s). Run tests using Test Explorer in Visual Studio or the .NET CLI where supported:

dotnet test CoreLibraryTest/CoreLibraryTest.csproj

If multiple test project targets exist, pick the appropriate test project variant for your environment.

Packaging

Many projects are intended to be used as class libraries and may be packaged as NuGet packages. Packaging can be done with the .NET CLI where applicable:

dotnet pack <project-file>

Consult individual project settings for package metadata and versioning.

Contributing

Contributions are welcome. Suggested workflow:

• Fork the repository and create a feature branch.
• Add or update unit tests for new behavior where applicable.
• Ensure the solution builds and tests pass locally.
• Submit a pull request with a clear description of changes.

License & Attribution

Copyright (c) Piero Viano. All rights reserved.

If a separate license file is present in the repository, consult it for license details.

Contact

For questions or issues, please open an issue in the repository or contact the maintainer.