Start with the version you actually run
Find out which .NET version the system uses and which other components it depends on. A system can consist of several projects and services that do not necessarily run on the same version.
Support matters more than the version number
What matters is whether the version still receives relevant security and maintenance updates. If support is nearing its end, there is an even stronger reason to plan an upgrade.
What could break?
An upgrade affects more than just .NET. Libraries, integrations, build environments and custom code may need to change. That is why the work should start with a review of dependencies and tests, not just a change of version number.
Upgrade step by step when possible
In larger or older systems, it is often better to break the work into smaller parts. That makes it possible to verify changes step by step and reduce the risk of a major outage.
Contact us
Do you need help assessing the upgrade?
We can review your existing .NET system and help you decide what needs doing now and what can wait.
