What is new in .NET 11, and should you move from .NET 10?
A fair tour of .NET 11 and C# 15 as released on 10 November 2026, the breaking changes to read first, and a decision guide for production teams on .NET 10.
· 7 min readSoftware care is our bespoke software support and maintenance service, for business-critical systems that have nobody left to look after them. We take it over, make it safe, and keep it that way, with a named senior engineer accountable for it.
Many organisations run on software that was built for them some years ago. It works, people depend on it, and the person or company that built it has moved on. Nobody is applying security updates, nobody is watching for faults, and nobody can say with confidence what would happen if it stopped.
Software care puts that right. We take over the system, close the gaps that have built up, and then look after it every month. You get a named senior engineer who knows your system, a plain-English report on its health, and the confidence that someone is responsible for it.
Software care begins with a software health audit of one system. The audit tells you where the system stands and gives you a fixed quote for onboarding and monthly care.
If you go ahead, onboarding gets the system into a state where it can be looked after properly:
Most of the value in software care is created before anything goes wrong. A system with tests, monitoring and a reliable release process is far easier to keep safe, and far quicker to fix when something does fail.
Many systems we take on have no automated tests and little documentation. We work backwards from the running system to write behaviour specifications and automated tests for what it does today. That gives us, and you, a safety net for every change that follows.
We collect diagnostic logs only, with controls designed to keep personal data out of them.
Most organisations come to us in one of these positions. Each has its own page.
We look after systems built with .NET (C#), including older .NET Framework applications, TypeScript and JavaScript, React and Next.js, hosted on Microsoft Azure and similar cloud platforms.
If the audit shows that a system is outside what we can safely support, we'll say so plainly and explain your options.
Many of the systems we take on are .NET Framework applications built ten or more years ago. Some run on versions of .NET, Windows Server or SQL Server that no longer receive security fixes, or soon won't. We add tests first, then upgrade in steps, and where it makes sense we move the application to Azure at the same time.
Software care is not ad hoc support by the hour. It's an ongoing contract, because looking after software properly needs continuity: the same engineers, the same knowledge of your system, and the preparation that stops small problems becoming large ones.
No. That's the usual starting point. The audit finds out how the system is built, hosted and released, and onboarding writes down what we learn so you're never in that position again.
It helps, but it isn't essential. With access to the code and the hosting, we can take a system over without the previous supplier's involvement.
Software care is a contract, because looking after software properly needs continuity. The engineer who looks after your system each month is the one who knows it. If you need a one-off piece of work, we're happy to talk about that separately.
We'll tell you at the audit, explain why, and set out your options. We would rather say so early than take on a system we can't look after safely.
We use AI agents under strict controls, and a named engineer approves anything that reaches a live system. Your data is never used to train models, and you can exclude any system or data from AI handling.

A fair tour of .NET 11 and C# 15 as released on 10 November 2026, the breaking changes to read first, and a decision guide for production teams on .NET 10.
· 7 min read
As of 10 November 2026, .NET 8 and .NET 9 no longer get security fixes. What has changed, what has not, and a calm 30-day plan for software on them.
· 4 min read
How a non-technical owner can decide what comes first on a product roadmap: plain criteria, simple scoring, outcome-based thinking, and saying no with reasons.
· 6 min readA software health audit gives you a plain-English view of the risks in one system, and what it would take to look after it properly. There's no obligation to continue.
Or call us on 01223 850035, Monday to Friday, 9am to 5pm.