Platform Evolution
Assessment run-2026-07-27-1 · 213 of 213 repos assessed
Repos / backoffice-pure360-subscription-manager

backoffice-pure360-subscription-manager

Windows Forms desktop tool for managing Pure360 marketing subscriptions and opt-ins, driving the Pure360 marketing WCF service and contact data in SQL Server.

36 · redmediumkernelOn-premZDD: not applicableothersecrets in source

Health score

36

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.

Runtime currency / 25
0
.NET Framework, out of mainstream support
Legacy transport / 15
6
Calls at least one legacy WCF endpoint
Test posture / 15
8
Some tests, coverage is thin
Security hygiene / 15
0
Credentials or keys committed to source
Dangerous coupling / 15
8
shares a core database (sqlserver:EventLog)
Activity / 10
10
Actively maintained
Deployment hygiene / 5
5
CI in place
Health over time
2026-07-24 (run-2026-07-24-1): 362026-07-27 (run-2026-07-27-1): 36
No change since 2026-07-24 (36 to 36).

Facts

Languagescsharp
FrameworksWindows Forms, log4net 2.0.17
Runtimes.NET Framework 4.6.2
Tests / CIsome / CI in place
Last commit2026-02-24
OwnerOwner unknown (mapping to be curated)
DomainCustomer communications (system generated; curate in repo-owners.json to override)
Product areaPhenix
HostedOn-prem Deployed to our own machines
  • Release "\marketing\pure360\backoffice-pure360-subscription-manager develop": TestQA: file copy to \\storage.travelcounsellors.com\builds\BackOffice\Pure360\Pu
  • Release "\marketing\pure360\backoffice-pure360-subscription-manager develop": LiveProviderQA: file copy to \\storage.travelcounsellors.com\builds\BackOffice\Pure360\Pu
  • Release "\marketing\pure360\backoffice-pure360-subscription-manager develop": DataFixQA: file copy to \\storage.travelcounsellors.com\builds\BackOffice\Pure360\Pu
  • Release "\marketing\pure360\backoffice-pure360-subscription-manager develop": OpsDev: file copy to \\storage.travelcounsellors.com\builds\BackOffice\Pure360\Pu
  • Release "\marketing\pure360\backoffice-pure360-subscription-manager release": Publish Live: task "Extract files Final"
Releases2 release pipeline(s): \marketing\pure360\backoffice-pure360-subscription-manager develop; \marketing\pure360\backoffice-pure360-subscription-manager release
Integrationwcf
SourceOpen in Azure DevOps

Risk flags

Each flag links to its glossary definition.

Dependencies in context

Laying out the graph…
greenamberreddata store (square, dashed link)Node size follows fan-in. Click any node to open it.

Entanglement

kernel Bound into the core by 2 mechanism(s).

Detaches when its WCF surface gains a modern interface or its WCF calls move to one; and when the shared database group it belongs to gains an owned API or completes schema separation (sqlserver:EventLog).

Depends on / used by

Used by (0)
No internal dependents.
Data stores
sqlserver:ContactApi1sqlserver:EventLog

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 applicable

Not a deployed service (libraries, database definitions, desktop apps) or a retirement candidate not worth the investment. Desktop application distributed to user machines; server-side ZDD does not apply.

SQL Server exit

Blocked by a shared core database

sqlserver:ContactApi1, sqlserver:EventLog are shared, so this system cannot change engine on its own: every sharer moves in convoy. The stage 4 work (named owner, declarative schema, owned API) has to land first; after that, the steps below apply to whatever slice this system ends up owning.

Blockers
Steps
  1. Inventory the schema and query surface of sqlserver:ContactApi1, sqlserver:EventLog: tables, stored procedures, triggers, cross-database joins and anything else engine-specific.
  2. Confirm the target: PostgreSQL (relational model; keep transactions and joins, swap the engine).
  3. Replatform to modern .NET first (see the recommended actions): current PostgreSQL and MongoDB drivers and EF Core providers target modern .NET, and doing one risky change at a time is cheaper than doing two.
  4. Data access is not through an ORM, so port the SQL by hand: translate T-SQL constructs, replace stored procedures with application code or target-native equivalents, and add integration tests around the queries that matter first.
  5. Stand up the target alongside SQL Server, backfill with an ETL pass (pgloader or an export/import job), then dual-write or replicate until parity is proven.
  6. Move reads to the target, watch correctness and latency, then cut writes over and keep SQL Server read-only until confidence is earned.
  7. Decommission the SQL Server database and remove the connection strings and firewall paths that pointed at it.

Containerisation

Not appropriate

This is a desktop application distributed to user machines; containers do not apply. Its modernisation path is replacement by a web application, not containerisation.

Recommended actions

Rotate the credentials committed to backoffice-pure360-subscription-manager

Risk flags indicate credentials or keys in source (hardcoded-secrets). Rotate now and enable secret scanning in CI; this is independent of all other work.

Impact: Closes a live security exposure at near-zero cost

proposed

Replatform backoffice-pure360-subscription-manager to modern .NET

Runs on .NET Framework 4.6.2, out of mainstream support. No pinning dependency blocks it; sequence by fan-in (providers before consumers). Shares sqlserver:EventLog, so batch it with its database group (stage 4).

Impact: Reduces the end-of-life runtime count

proposed

Assessment notes

backoffice-pure360-subscription-manager

Purpose

Internal Windows desktop application ("Subscription Manager") used by marketing/back-office staff to manage Pure360 email-marketing subscriptions: opting contacts in/out, running marketing functions and CSV-based data operations against contact data.

Tech stack

  • .NET Framework 4.6.2 WinForms executable (TC.Marketing.SubscriptionManager, WinExe) with supporting libraries: TC.ContactCentre.MarketingServices (controller layer), TC.ContactCentre.MarketingFunctions.DAL (SQL data access) and a custom config-section project.
  • log4net logging into the EventLog SQL database; YamlDotNet; Microsoft.Extensions.DependencyInjection; TC.ConnectionBroker (including the WCF extension) for connection/endpoint resolution.
  • Per-environment app.*.config transforms (qa, preproduction, production); environment selectable via command-line argument.

Deployment

Prod application with 2 releases. Build pipelines "backoffice-pure360-subscription-manager-develop" and "-release"; release pipelines under \marketing\pure360\. Per the README, CI/CD publishes builds to a storage network share (folders for TestQA, DataFixQa, LiveProviderQA, OpsDev) that users launch through the internal Application Launcher. No YAML pipeline in the repo (classic definitions).

Dependencies

  • Internal: backoffice-pure360-marketing-service-api — the app calls its WCF service via Pure360WcfServiceClient (types from TC.Pure360.MarketingService.Shared) for opt-in/opt-out operations; tc-connectionbroker for connection-string/endpoint brokering.
  • External: Pure360 email-marketing platform (indirectly, via the marketing service API).

Data stores

  • SQL Server ContactApi1 database (direct DAL access via connection broker) for contact/marketing data.
  • SQL Server EventLog database as the log4net logging sink (credentials embedded in config transforms).

Integration points

  • Outbound WCF/SOAP calls to the Pure360 marketing service; direct SQL access to contact data.
  • No inbound interfaces — it is an operator-driven desktop tool.

Code health

  • Unit tests present (TC.Marketing.SubscriptionManager.Tests: DAL, CSV helper, data-translator, marketing functions) — moderate coverage.
  • Practical README covering build, versioning (version.props) and deployment; actively maintained (last commit 2026-02-24).

Modernisation risks

  • .NET Framework 4.6.2 WinForms client distributed via a network share and app launcher — dependent on Windows desktop estate and domain connectivity.
  • Coupled to the legacy WCF marketing service and direct database access; hard-coded SQL credentials in config transforms.