Techbanq

Stacks · enterprise systems

.NET earns its place from the estate around it

When the directory that signs your staff in, the documents they work in and the servers you license are already Microsoft, a .NET application inherits identity, integration and operations the day it is born. That inheritance is an engineering argument — and it deserves to be weighed, not assumed.

Information security for software delivery

  • ISO

    ISO/IEC 27001

    ISO/IEC 27001 certified

Certifications & registrations

The honest fork

Modern .NET, the legacy Framework, and the three positions between them

"Migrate everything" is a slogan, not an assessment. For each legacy application there are three defensible positions, and the right one depends on how much the application still changes and how long it must live.

OptionWhat it costs nowWhat it costs over yearsThe risk it carriesBest for
Stay on .NET FrameworkNothing — the application keeps running as it is.A widening gap: the Framework receives maintenance, not investment, so every year buys less future.Low today, compounding — Windows-only hosting, an ageing library ecosystem, a shrinking hiring pool.Stable systems that rarely change and have a planned retirement.
Migrate to modern .NETA real project — dependencies, APIs and hosting assumptions all need review, and some rewrites.A platform under active investment: cross-platform hosting, container deployment, current performance work and long-term-support releases.The migration itself — bounded by doing it incrementally, service by service, rather than as one cutover.Applications still under active development with years of life ahead.
Replace rather than migrateThe largest effort — but honest when the application no longer fits the business it serves.A system designed for what the organisation does now, not a faithful port of what it did then.Scope risk — managed by treating it as new product work with the legacy system as evidence, not as a migration.Systems whose real problem is the business fit, not the runtime.

The estate argument

What a .NET application inherits from a Microsoft-centred organisation

In most Saudi enterprises and government-adjacent organisations, the Microsoft layer is already load-bearing: the directory holds every employee identity, the mail and documents live in the Office ecosystem, and Windows servers are licensed, monitored and patched by an operations team that knows them. A .NET application drops into that estate natively — staff sign in with the account they already have, permissions follow groups the organisation already maintains, and the application appears inside the collaboration tools people already work in rather than as another browser tab with another password.

The same argument, run in reverse, is why we do not recommend .NET everywhere: an organisation whose identity, operations and skills are centred elsewhere would be buying integration with an estate it does not have. And the platform itself has changed shape in a way buyers should know: modern .NET is cross-platform and container-friendly, so choosing it no longer means choosing Windows hosting — the estate argument today is about identity, ecosystem and people far more than about servers.

The integration surface

The three Microsoft integrations that carry most .NET business value

These are the connections enterprise buyers actually ask for, and where the platform’s adjacency to the rest of the Microsoft estate does visible work.

01

Identity from the directory

Sign-in, roles and access reviews flow from the organisation’s existing identity directory: joiners get access from their group memberships, leavers lose it the day the directory says so, and the application never keeps a password store of its own to breach or forget.

02

Work inside the Office ecosystem

The documents, sheets and approvals a process produces land in the collaboration environment staff already use — generated reports as real Office documents, tasks and notifications surfaced where people already look, instead of another portal competing for attention.

03

Data with the estate’s tools

Reporting and analytics connect through the business-intelligence tooling the organisation has already licensed and learned, so a new application extends the existing reporting landscape rather than founding a parallel one.

The support horizon

Long-term support is the release policy enterprises actually buy .NET for

An enterprise system is budgeted, audited and staffed on a horizon of years, and it needs a platform whose support horizon is published rather than implied. Modern .NET ships on a predictable cadence with designated long-term-support releases, each with a public end-of-support date — which means an upgrade is a planned line in next year’s budget, not a surprise discovered when a vulnerability lands on an unsupported runtime. We build on the long-term-support releases by default and treat staying inside the supported window as an operational requirement, the same as patching.

The same lens is how we frame the legacy question without drama. A .NET Framework application is not about to stop working; it is on a platform in maintenance, and the practical question is whether the application will still be changing when the gap between maintenance and investment starts to bite. Applications with active roadmaps justify migration; stable ones with planned retirements often do not. That judgement is made per application, with its owners, from its roadmap — not from a modernisation slogan.

Our role

How we run a .NET engagement across new builds and legacy estates

  1. 01

    The fit, argued both ways

    We make the estate argument honestly in both directions — recommending .NET where your Microsoft estate makes it the natural home, and something else where it does not, because we sell engineering rather than a platform.

  2. 02

    Migration by verdict, not by slogan

    Each legacy Framework application gets its own verdict — stay, migrate or replace — from its roadmap and its risk, and the migrations we do run are incremental, service by service, never a single cutover night.

  3. 03

    Built to the support calendar

    New systems land on long-term-support releases with the upgrade path budgeted from day one, so staying supported is routine maintenance in your plan rather than a periodic crisis.

Which systems the business needs and in what order is your portfolio decision; we make sure each one lands on a supported platform, signs in with your directory, and lives comfortably inside the estate you already operate.

Common questions

What buyers ask

Does choosing .NET still mean choosing Windows servers?+

No — that coupling belonged to the legacy .NET Framework. Modern .NET runs on Linux as comfortably as on Windows, deploys in containers, and fits the same cloud-native hosting patterns as any current platform. In practice many of the modern .NET services we build run on Linux hosts precisely because that is the cheaper, simpler operational choice. The estate argument for .NET today is about identity, the Office ecosystem, existing licensing and team skills — not about the operating system underneath, which has become a hosting decision like any other.

Our core system runs on .NET Framework. How urgent is a migration, honestly?+

Less urgent than a vendor pitch implies, and more urgent than doing nothing implies. The Framework still receives maintenance, so a stable application is not in immediate danger. The costs are gradual: hosting stays Windows-only, the surrounding library ecosystem ages, new platform investment goes elsewhere, and hiring for it slowly hardens. Our test is the application’s own roadmap — if it will still be actively changing in a few years, migrating while change is routine beats migrating under pressure later; if it is stable with a planned retirement, a migration may simply be money spent making its last years more modern. We give that verdict per application, in writing.

We are not a Microsoft-centred organisation. Would you still recommend .NET to us?+

Probably not, and that is the estate argument working as it should. .NET is a capable, well-supported platform on its own merits, but most of its enterprise advantage comes from adjacency — the directory-based sign-in, the Office ecosystem, the licensing and the operational skills you would already have. Without that estate, you would be paying the platform’s learning and hiring costs while collecting few of its integration benefits, and a stack aligned with your existing identity provider, tooling and team is likely the better engineering answer. We would rather tell you that in the assessment than bill you for discovering it in year two.

Next step

Assess the fit with us

An estate review that says where .NET fits your systems, which legacy Framework applications justify migration, and which are fine where they are.

Assess the fit with us

What happens next

  1. 1We reply within one business day.
  2. 2A 30-minute scoping call with a senior consultant.
  3. 3A written proposal with scope, team, and timeline.

Or reach us directly

By submitting this form you agree to our Terms of Use and Privacy Policy.