Rescue for .NET applications and APIs
.NET Project Rescue
Your .NET application runs on an end-of-life version, a security review found problems, or releases still depend on one person. We assess what is wrong, stabilize it, and hand it back to your team, running.
What goes wrong in .NET projects
An end-of-life runtime
The application runs on a .NET version that no longer gets security fixes, and the upgrade keeps moving down the list.
An identity server at end of life
Sign-in depends on IdentityServer4 or a custom login that stores credentials in the application's own database, with no second factor.
Services that trust every caller
Internal APIs accept requests without verifying who sent them, so one weak point exposes everything behind it.
Secrets in code and configuration
Passwords and keys sit in appsettings files and source code, where anyone with the repository can read them.
Manual releases and database changes
Schema changes are applied by hand, and nothing stops a build for one environment from reaching another.
Infrastructure someone else controls
The repositories, pipelines or Azure subscription belong to a former vendor, so you cannot change your own system safely.
How the rescue works
Assess, stabilize, hand it back. The same three steps as every Briebug rescue, applied to this stack.
Assess
Find out exactly what is wrong before you commit to fixing it.
- A fixed-fee review of the .NET code, the runtime and dependencies, authentication, the architecture, the pipeline and security
- A supported upgrade path for the runtime and for sign-in
- A triage report of what to fix in what order, and a milestone-based estimate
Stabilize
Stop the bleeding first. Then deliver the roadmap.
- Upgrade to a supported .NET LTS release, and keep authentication working while you plan its replacement
- Make every service verify every caller, and move secrets into a vault such as Azure Key Vault
- Put schema changes in the pipeline, pin builds to their environment, and add security scanning to every change
- Move repositories and pipelines into an environment you own, then deliver the roadmap
Hand it back
A project your team can run without us.
- Documentation of what we changed and why
- Pairing with your engineers until they own the .NET code and the process
- An optional senior oversight retainer after handback
Case studies
PSIA / SnowPro
Education, certification and membership platform for ski instructors
Angular 7 to 17and .NET Core 3.1 to .NET 8 (LTS)
- Problem
- Angular 7 and .NET Core 3.1 nearing end of life, failing test suites, and infrastructure that depended on a third party.
- What we found
- Jest and Cypress suites that broke during the upgrade, an end-of-life identity server, WordPress plugins that failed on PHP 8, and a planned Azure subscription transfer that risked major downtime.
- Result
- Angular 7 to 17, .NET Core 3.1 to .NET 8, working test suites, and repositories, pipelines and documents in an Azure DevOps environment PSIA owns.
Strata GPO
Member portal for a group purchasing organization
2,137customer accounts created in Microsoft Entra on release night, with zero errors
- Problem
- An independent security assessment flagged critical weaknesses in a live portal that thousands of members use every day.
- What we found
- Credentials stored in the portal's own database with no second factor, internal services that did not check callers, hardcoded secrets, and manual releases.
- Result
- MFA sign-in through Microsoft Entra, every service verifying every caller, secrets in Key Vault, and automated, scanned releases. 2,137 accounts migrated with zero errors.
CareMetx
Healthcare patient-support services company with end-customer portals
- Situation
- CareMetx wanted to modernize its end-customer portals and level up its internal team at the same time.
- What we did
- We embedded React and .NET developers, a solution architect and a scrum master to build portal features and mentor the team.
- Result
- The engagement ran from July 2020 into 2022, with client NPS scores of 8 to 10.
More .NET case studies
- Brandfolder: integrations, an Office add-in and a growing engineering team
- Eberl Claims: an embedded team that shipped a cross-platform adjuster app
More rescues, on every stack, in all case studies.
Start with the Technical Assessment.
A fixed fee of $10K and about one week. You get a comprehensive report, a triage report of what to fix in what order, and a milestone-based estimate for the work.