C# and .NET support

Keep your C# and .NET systems running

A good deal of what we look after is C# that somebody else wrote years ago and that still does a real job. We keep it patched, fix what breaks and move it off versions that have fallen out of support.

Tell us about your system

Sounds familiar

Older .NET systems that still matter

The code still works. What is missing is anybody who can change it safely.

Nobody left knows it

It has run for years and the person who wrote it has moved on. Changing it feels like a gamble, so nobody does, and it quietly falls further behind.

It is on an old version

The .NET version, the libraries or the server underneath have fallen out of support. The security updates have stopped coming.

Small things keep breaking

A certificate expires, an overnight job fails or an operating system update breaks something nobody has looked at in years.

What we work on

Large systems and small ones

Our C# work ranges from large systems built for corporations to small internal tools. Each one gets the same care.

Most of the .NET work that reaches us now is already in production and somebody depends on it every day.

We work in C#, .NET, JavaScript and Node.js. We do not work in C, C++ or Rust.

How it goes

From an unknown system to a routine one

Nothing gets upgraded before we understand what is there. Each step makes the next one safer.

Review

We get the code building and running and find out how it is deployed, including any steps that were never written down.

Make it safe

What the upgrade needs to be checked at every step. Source control, a build you can repeat, a test environment and logs.

Upgrade

Move it onto supported versions one piece at a time, with each piece tested before the next one starts. The .NET version, the libraries and the server it runs on.

Look after it

Security patches, library updates and the small fixes that come up once it is back in regular use.

Questions about .NET support

What people ask first

Can you support a .NET application you did not build?

Yes. Most of the .NET code we look after was written by somebody else, often years ago. We learn how it works before we change any of it.

Do we have to rewrite it to get onto a supported version?

Not necessarily. Part of the first review is working out what can be upgraded as it stands and what is better rewritten. You get that in writing, ordered by risk, before anything is decided.

Will you work alongside our own developers?

Yes. We can take on one system your team has no time for or cover an application they inherited and would rather not own.

What about the database?

We work in SQL Server as well as the code, and the database gets the same review. How big it is, how it is backed up and whether a restore has ever been tested.

Related services

Tell us about your .NET system

What it does, roughly how old it is and what is worrying you about it. We will come back with questions and a clear answer on what it would take.

Get in touch Or email sales@tektology.com directly.