When we reach for it
Enterprise systems where the client already runs .NET, and modernisation work lifting Framework applications onto the current runtime — usually the single highest-value piece of work available in such an estate.
Web and application frameworks
.NET development
A mature application platform with first-class tooling, a strong runtime and a straight path from an on-premises Windows estate to something that can be deployed like anything else.
What we reach for first
When we would argue against it
We do not introduce it to teams with no Microsoft background. Its advantages are largely organisational, and they evaporate when nobody on the client side can operate it.
What it looks like in delivery
The migration is rarely the hard part. The hard part is discovering what the application actually does, which is why we put characterisation tests around observed behaviour before we move anything, and move it in pieces afterwards.
Where this appears on the site
Published work that names it
Derived from the stacks published on those pages, not written here — so this list cannot claim something the page it points at does not say.
Working in .NET?
Tell us what it is running, what it costs you today, and what you need it to do next. A senior engineer will tell you what we would keep and what we would change.