JamesConsulting 2.0.0

JamesConsulting

A small, opinionated grab-bag of extension methods, helpers, and primitives shared across all James Consulting LLC libraries. Multi-targets netstandard2.0, netstandard2.1, net9.0, and net10.0 so it can drop into virtually any .NET project.

Install

dotnet add package JamesConsulting

<PackageReference Include="JamesConsulting" Version="2.0.*" />

Trusted Publishing: every JamesConsulting package on nuget.org is published via NuGet Trusted Publishing from this repo's ci.yml workflow (no long-lived API keys), and signed with Azure Trusted Signing under the James Consulting LLC identity.

What's included

All public APIs ship with XML documentation; downstream consumers get IntelliSense + SourceLink for step-into debugging.

📚 Full API reference: https://docs.jamesconsulting.biz/james-consulting-core/ (generated with DocFX from master).

What's new in 2.0

This is a breaking modernization. If you're upgrading from 1.x, read this list:

• Dropped legacy target frameworks. Now multi-targets netstandard2.0, netstandard2.1, net9.0, net10.0. Removed: net5.0, net6.0, net7.0, net8.0, net462, netcoreapp3.1.
• Removed Metalama / PostSharp dependencies. Argument validation that previously relied on Metalama contracts ([Required], [NotEmpty], [StrictlyPositive], etc.) is now provided by an internal Guard helper modelled on ArgumentNullException.ThrowIfNull. Exception types (ArgumentNullException / ArgumentException / ArgumentOutOfRangeException) and ParamName values are preserved against the v1.x contract. Exception messages and a few specific shapes changed — most notably MethodInfoExtensions.CreateTaskResult now throws a clear ArgumentException for non-Task<T> return types instead of bubbling a reflection-internal ArgumentException out of MakeGenericType. The library no longer pulls Metalama into your build graph.
• Trimmed transitive surface. Single hosting reference (Microsoft.Extensions.Hosting.Abstractions 10.0.0).
• macOS / Linux behavior. ConnectToSharedFolder.Connect() throws PlatformNotSupportedException on non-Windows OSes (it wraps Win32 WNetAddConnection2W). Dispose() and the finalizer are safe no-ops on those platforms instead of DllNotFoundException-crashing tests.
• Centralized package metadata via src/Directory.Build.props (Authors, Company, Copyright, deterministic builds, embedded source, NBGV, SourceLink). No per-file copyright headers anymore.
• Continuous deployment. Single ci.yml GitHub Actions workflow replaces the old split build/publish workflows and the legacy Azure DevOps pipeline.

Build & test

# from repo root
dotnet restore src/JamesConsulting.sln
dotnet build   src/JamesConsulting.sln --configuration Release
dotnet test    src/JamesConsulting.sln --configuration Release

Single TFM:

dotnet test src/JamesConsulting.Tests/JamesConsulting.Tests.csproj --framework net9.0

Filter to a single test:

dotnet test --filter "FullyQualifiedName~ObjectExtensionsTests.Mask"

Release process

Releases follow GitFlow + semver. The ci.yml workflow has three jobs:

Cutting a release:

# 1. cut release branch from develop
git switch develop && git pull
git switch -c release/2.0.0
git push -u origin release/2.0.0
# -> publish-rc fires automatically: 2.0.0-rc.<run>

# 2. when QA approves, merge release/2.0.0 -> master, then tag from master
git switch master && git pull
git tag v2.0.0
git push origin v2.0.0
# -> publish-stable fires: 2.0.0 stable + GitHub Release

# 3. back-merge master -> develop
git switch develop
git merge --no-ff master
git push

The major.minor.patch number lives in version.json. Bump it before opening the release branch.

Contributing

1. Branch from develop (feature/<name> or bugfix/<name>).
2. Tests first — this repo follows BDD/TDD with a 90% coverage target.
3. Run dotnet build and dotnet test locally before pushing.
4. Open a PR into develop. CI must be green and Sonar quality gate must pass.

Repo conventions live in AGENTS.md.

License

MIT © James Consulting LLC