lib-repository
Shared NuGet library providing a generic repository/query-handler pattern (TC.Repository) plus Dapper-based base implementations (TC.Repository.Dapper) for data access across the estate.
Health score
0 to 100 across seven weighted factors; nothing is hidden. Green is 75 and above, amber 50 to 74, red below 50. How scoring works.
Facts
| Languages | csharp |
| Frameworks | Dapper 1.50.4, MSTest 1.2 |
| Runtimes | .NET Standard 1.1, .NET Standard 2.0, .NET Framework 4.5.1 |
| Tests / CI | some / CI in place |
| Last commit | 2018-01-19 |
| Owner | Owner unknown (mapping to be curated) |
| Domain | Platform services (system generated; curate in repo-owners.json to override) |
| Product area | Shared platform |
| Hosted | No signal No hosting signal in its pipelines (typical for libraries and contract packages) |
| Releases | 2 release pipeline(s): \finance\lib-repository develop; \finance\lib-repository release |
| Integration | - |
| Source | Open in Azure DevOps |
Dependencies in context
Entanglement
loose No binding mechanisms apply: this system needs no untangling work.
Depends on / used by
Migration playbooks
Generated from this repo's assessment data: what is feasible, what blocks it, and the steps in order. Ratings: green means actionable now, amber means sequence other work first, red means blocked, grey means not applicable.
ZDD adoption
Not applicableNot a deployed service (libraries, database definitions, desktop apps) or a retirement candidate not worth the investment. Ships as a package; ZDD applies to the services that consume it.
SQL Server exit
Not applicableNo SQL Server dependency is recorded for this repo. Nothing to migrate.
Containerisation
Not applicableLibraries ship as packages, not as running services. There is nothing to containerise.
Recommended actions
Review lib-repository for retirement
Dormant (last commit 2018-01-19) yet still release-linked, and nothing depends on it. Confirm remaining use, then retire and disarm its pipeline.
Impact: Shrinks the estate before the expensive work begins
proposedAssessment notes
lib-repository
Purpose
Class-library repo that publishes two NuGet packages: TC.Repository (read/write repository interfaces, query handlers, paging helpers, Maybe type) and TC.Repository.Dapper (Dapper base classes for query handlers and repositories, custom property/parameter mapping). Consumed by other estate services for SQL data access.
Tech stack
C# class libraries. TC.Repository targets .NET Standard 1.1; TC.Repository.Dapper multi-targets .NET Standard 2.0 and .NET Framework 4.5.1 and depends on Dapper 1.50.4 (2018-era version). Packages are versioned in the csproj (1.2.0 / 1.3.0) with GeneratePackageOnBuild.
Deployment
Included with 2 releases. Two classic build pipelines (lib-repository develop, lib-repository release) and matching release pipelines under \finance\. No YAML pipeline in the repo; a build/SetBuildVariable.ps1 script supports the classic build.
Dependencies
No internal estate dependencies; the only third-party package is Dapper. No external services are called.
Data stores
None directly - it provides abstractions used by consumers against SQL Server via Dapper, but holds no connection strings itself.
Integration points
None; it is a pure library with no network or messaging integrations.
Code health
One small MSTest project (TC.Repository.Tests) covering the Maybe type only - minimal coverage. CI exists via classic pipelines. Last commit 2018-01-19, so the repo has been dormant for over eight years while still being deployed/consumed.
Modernisation risks
Very old targets (.NET Standard 1.1, net451) and an eight-year-old Dapper version; the library is frozen while downstream services evolve. Any consumer moving to modern .NET may need this retargeted or replaced. Medium priority mainly because breakage risk is low but the package pins consumers to legacy dependency versions.