tc-useraccount-telephonecontracts-servicecontract
Two-class contract NuGet package (TC.UserAccount.Telephony.ServiceContract) defining the UserAccountTelephony DTO and telephone-package enum shared between the telephony contracts API and its consumers.
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 | - |
| Runtimes | .NET Standard 2.0, .NET Framework 4.6 |
| Tests / CI | none / CI in place |
| Last commit | 2020-01-02 |
| Owner | Owner unknown (mapping to be curated) |
| Domain | Identity and access (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 | 1 release pipeline(s): \finance\live-agent\tc-useraccount-telephonecontracts-servicecontract |
| 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
Replatform tc-useraccount-telephonecontracts-servicecontract to modern .NET
Runs on .NET Standard 2.0, .NET Framework 4.6, out of mainstream support. No pinning dependency blocks it; sequence by fan-in (providers before consumers).
Impact: Unblocks 1 dependent system(s)
proposedAssessment notes
tc-useraccount-telephonecontracts-servicecontract
Purpose
The shared contract for the live-agent telephony domain: a UserAccountTelephony DTO (payment telephone id, user account id, CLI id, contract dates, up to three phone numbers, audit fields) and the UserAccountTelephonePackage enum (Phone, PhoneCallRecording, PhoneInternet, PhoneInternetCallRecording, HeadOffice) with DataContract attributes for WCF-style serialisation. Consumed by tc-useraccount-telephonecontracts-api (which references version 1.0.7) and any other telephony clients.
Tech stack
Single C# class library multi-targeting netstandard2.0 and net46, version 1.0.7 with GeneratePackageOnBuild. No package dependencies at all.
Deployment
Included with 1 release: classic build pipeline tc-useraccount-telephonecontracts-servicecontract release and release pipeline \finance\live-agent\tc-useraccount-telephonecontracts-servicecontract (no YAML in repo; build/SetBuildVariable.ps1 and SetBetaFlag.ps1 support the classic build). "Deployment" is NuGet publication only.
Dependencies
None, internal or external — it is a pure POCO contract package.
Data stores
None, though its DTO mirrors the UserAccountTelephony table shape in the shared UserAccount database.
Integration points
None directly; the DataContract/EnumMember attributes exist so the types serialise over WCF as well as JSON.
Code health
No tests (nothing meaningful to test), and notably no README at all. Dormant since 2020-01-02, frozen in lockstep with the API repo that consumes it.
Modernisation risks
Low as a standalone artefact — two files with zero dependencies retarget trivially. Its fate is tied to tc-useraccount-telephonecontracts-api: if that API is folded into backoffice-useraccount-service or rebuilt, this package should be absorbed or retired with it, and the net46 target dropped.