.NET modernisation while the business keeps running.
For businesses running on an older .NET system that has become risky to change, where nobody left knows it end to end.
Signs it is time
The system still does its job, and the business depends on it. Changing it is the problem. Some of these usually apply:
- It runs on .NET Framework, or on a version of .NET Core or .NET that Microsoft no longer supports.
- Releasing a change needs one particular person, or a manual checklist run after hours.
- It is hosted on Windows servers that are overdue for an upgrade.
- Its libraries are no longer maintained, and some have known security problems.
- The people who built it have moved on, and nobody knows all of it.
How we modernise it
We start by mapping what the system does and who relies on it: screens, integrations, scheduled jobs and the reports people depend on. Then we put automated tests around the behaviour that matters, so a change that breaks something shows up before release.
The work goes in stages. We move or replace one part at a time, and each part is released on its own. Where it helps, the old and new versions run side by side until the new one has proved itself. The business keeps using the system the whole way through.
If it suits you, the system can move to cloud hosting with its infrastructure defined as code. It can also stay on your own servers.
What you have at the end
A system on a supported version of .NET, with automated builds and deployment, tests that run on every change, and monitoring. You also get a written record of the main decisions, and we walk your team through it.
Work we have done
GenTwo is a display platform that gaming venues have run for years. We are replacing it in stages while venues keep using it every day.
NistCheck and Reveal are both built on C# and modern .NET, so we build new systems on the platform as well as moving old ones to it.
Ways to start
Get in touch
Email or call us, or book a chat.
Staged delivery
Each stage has its own budget, timeframe and acceptance criteria, so you can pause or reorder between stages.
Ongoing support
Time set aside each month, with agreed response times for urgent issues.
Questions
Should we rewrite it from scratch?
Usually not in one go. A full rewrite puts all the risk on one switchover date and holds back improvements until it lands. Sometimes a part is worth rebuilding, and the review says which.
Do we have to stop feature work?
Not usually. Small releases leave room for urgent changes, and some modernisation can happen as part of feature work in the same area of the code.
Can you work with our own developers?
Yes. We work in your repository and your delivery process, and your team learns the new structure as it goes in.
Tell us about the system.
What it does, what it runs on, and what worries you about changing it. You will hear back from one of our engineers within a couple of days.