phenix-content-ui-web
ASP.NET MVC/WebForms site on .NET Framework 4.7.2 that serves Phenix content pages and proxies, resizes and crops supplier (TTI/GIATA) images via ASHX handlers using encrypted image URLs.
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, javascript, typescript |
| Frameworks | ASP.NET MVC 5, ASP.NET Web API 2, Gulp 3 |
| Runtimes | .NET Framework 4.7.2 |
| Tests / CI | none / CI in place |
| Last commit | 2026-05-06 |
| Owner | Owner unknown (mapping to be curated) |
| Domain | Content and destinations (system generated; curate in repo-owners.json to override) |
| Product area | Phenix |
| Hosted | On-prem Deployed to our own machines
|
| Releases | 2 release pipeline(s): \ops\phenix-content-ui-web\phenix-content-ui-web; \ops\phenix-content-ui-web\phenix-content-ui-web Stealth |
| Integration | rest |
| Source | Open in Azure DevOps |
Risk flags
Each flag links to its glossary definition.
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
A long roadTechnically eligible one day, but the blockers are structural: hosted WCF or SOAP contracts that cannot run two versions at once, or heavy legacy coupling. Sequence the modernisation work first. Legacy web front end: session state and framework age make mixed-version fleets risky until state is externalised.
- Adopt the four-stage discipline from the ZDD engineering standard: pre-deployment compatibility, deployment, feature activation behind a flag, post-release cleanup.
- Raise automated test coverage first: ZDD trades the end-of-sprint manual gate for continuous automated confidence, so the tests are the entry ticket.
- Make every change dual-version safe: backwards-compatible APIs (new major version for breaking wire changes), expand and contract for any schema change, and consumers tolerant of unknown fields.
- Externalise any remaining session state so users can move between nodes mid-session without disruption.
- Wrap behaviour changes in feature flags so code deploys dark and release becomes a business decision, not a deployment event.
- Route deployments through the Workflow Engine's automated drain, deploy, health-check, return cycle (the path proven by the first automated production run in mid-2026).
- Verify with area-scoped regression rather than the whole-platform cycle, and watch error rates after rollout with automated rollback on alert.
SQL Server exit
Not applicableNo SQL Server dependency is recorded for this repo. Nothing to migrate.
Containerisation
Feasible after replatformingAppropriate, but the .NET Framework runtime has to go first; container work rides along with the replatform rather than preceding it.
- .NET Framework only runs on Windows; practical (Linux) containers need modern .NET
- Replatform to modern .NET first (see the recommended actions). Containerising then becomes routine.
- Add a Dockerfile and make the app read all configuration from environment variables and the secrets manager, never from machine-local files.
- Log to stdout and expose a health check endpoint so ECS can supervise it.
- Adopt the shared ci.yml pipeline template with the container parameters (awsRegion, containerAfterBuild, ecsTerraformRepo), which is exactly how the estate's existing AWS services deploy.
- Define the service in the Terraform repo, deploy to a non-production environment, then shift traffic and disarm the deployment-group release pipeline.
Recommended actions
Rotate the credentials committed to phenix-content-ui-web
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
proposedReplatform phenix-content-ui-web to modern .NET
Runs on .NET Framework 4.7.2, out of mainstream support. No pinning dependency blocks it; sequence by fan-in (providers before consumers).
Impact: Reduces the end-of-life runtime count
proposedAssessment notes
phenix-content-ui-web
Purpose
"Phenix Content" — a small content-serving site with two MVC controllers (Home, LoadingBox) and three ASHX handlers: ImageResizer and ImageCropper fetch remote supplier images (following encrypted URLs that can embed basic-auth credentials for TTI/GIATA sources) and resample them, and MapView renders an embedded Bing Maps (virtualearth) page. Frontend assets are Sass/TypeScript built with Gulp using the internal @tc/web-styles package.
Tech stack
Single C# project on .NET Framework 4.7.2, legacy csproj with packages.config: ASP.NET MVC 5, Web API 2, Razor views, Newtonsoft.Json, System.Drawing-based image resampling. Node toolchain is dated (Gulp 3.9, gulp-tsc, lite-server). New Relic APM configured via NewRelic.AppName.
Deployment
prod_application with 2 releases. Build pipeline phenix-content-ui-web CI (classic — no pipeline YAML in the repo, just a build.bat); release pipelines \ops\phenix-content-ui-web\ main and Stealth. Seven per-environment Web.*.config transforms; hosted under IIS alongside the wider Phenix web estate.
Dependencies
Internal: only TC.Exceptions (tc-exceptions) — no ConnectionBroker, no other TC packages. External: TTI/GIATA supplier image sources (URLs produced by a separate "GIATA Downloader" that encrypts them), Bing Maps mapcontrol, New Relic.
Data stores
None. The site holds no connection strings and owns no database; it proxies remote images and serves static/bundled content.
Integration points
Inbound HTTP only (MVC pages plus the ASHX image/map handlers). Outbound HTTPS requests to supplier image hosts, sometimes with credentials extracted from the decrypted URL payload.
Code health
No test projects, no README, and a hardcoded AES key/IV pair in Decryptor.cs (shared by convention with the GIATA Downloader) — effectively a secret in source. The MapView handler references the long-retired Bing Maps v6.1 control over plain http. Still minimally maintained (last commit 2026-05-06 was an XSS fix), which suggests it is security-sensitive but under-invested.
Modernisation risks
Medium: small and self-contained, so a rewrite to a minimal .NET 8 image-proxy service would be cheap, but the current form is a legacy MVC/WebForms hybrid with an SSRF-shaped image proxy (ImageUrl query string fetched server-side), hardcoded crypto keys, and a dead map dependency. The encryption contract with the GIATA Downloader must be migrated in step.