Skip to content

Service · Backend

.NET Development Services

Commission us to build ASP.NET Core applications in C#, or to bring a .NET Framework system onto modern .NET. We deliver the APIs, data layer and deployment, and leave your developers a solution that builds and tests cleanly.

ASP.NET Core on an LTS release

Framework-to-modern upgrade plans

EF Core migrations run by the pipeline

Deliverables

What a .NET development engagement delivers.

01Delivered

ASP.NET Core APIs

Minimal APIs or controllers with validation, problem-details error responses, versioning and generated OpenAPI documents.

02Delivered

Data layer on EF Core

Entity Framework Core models and migrations applied by the release pipeline, with Dapper wherever hand-written SQL reads more clearly.

03Delivered

Identity and authorisation

Microsoft Entra ID, ASP.NET Core Identity or another OpenID Connect provider, with policy-based checks on each endpoint.

04Delivered

Framework-to-modern upgrade

Projects moved from .NET Framework to current .NET, using the upgrade assistant where it helps and rewriting System.Web dependencies where it cannot.

05Delivered

Background work and hosting

Hosted services or worker processes for queues and schedules, deployed to Azure App Service, containers or Linux hosts.

Early decisions

Technical decisions we settle early in .NET development.

01Decided

Minimal APIs or controllers

Minimal APIs for small, focused services; controllers where filters and conventions keep a larger API consistent.

02Decided

LTS or STS release

Which .NET release to target, and when the next upgrade falls due under Microsoft’s published support policy.

03Decided

Front end

Blazor, Razor Pages, or a separate React or Angular client talking to the API.

04Decided

EF Core or Dapper

Where the ORM saves effort and where raw SQL is faster to run and easier to reason about.

05Decided

Hosting target

Windows or Linux, App Service or Kubernetes, which shapes how configuration, secrets and logging are wired.

Engagement

How a .NET development engagement runs.

  1. 01Phase 1

    Solution and package review

    We review projects, NuGet packages and Windows-only dependencies, and identify what blocks a move to modern .NET.

  2. 02Phase 2

    Upgrade in place or strangle

    Small solutions are upgraded project by project; large ASP.NET MVC sites are fronted by YARP so routes move to ASP.NET Core gradually.

  3. 03Phase 3

    Build on modern .NET

    New features and migrated modules arrive with xUnit tests that run on every pull request.

  4. 04Phase 4

    Deploy and decommission

    Workloads move to the chosen host, old IIS sites are retired as traffic leaves them, and documentation is passed over.

Fit

When .NET is the right choice.

01Good fit

Microsoft-aligned organisations

Companies on Azure, Microsoft 365 and Entra ID, where .NET slots in with little integration work.

02Good fit

Ageing .NET Framework systems

Business-critical applications on Framework 4.x that need to run on Linux, in containers or on a runtime with active support.

03Good fit

Typed, high-throughput APIs

Teams who value C#’s type system and the request throughput ASP.NET Core can sustain on busy services.

Two different .NETs

.NET Framework 4.x is Windows-only and receives fixes but no new features. Modern .NET, which grew out of .NET Core, is cross-platform and ships a new major version every November. Many organisations run both, and keeping the old one alive grows costlier as libraries drop support for it.

Migrating large ASP.NET applications in slices

Rewriting a large MVC or Web Forms application in one go is risky. Microsoft’s YARP reverse proxy lets a new ASP.NET Core app sit in front, serving migrated routes itself and forwarding everything else to the old site. Each slice ships on its own, and the old app shrinks until it can be switched off.

EF Core in production

EF Core is productive, but the SQL it generates deserves review on busy paths. We log queries in development, use AsNoTracking for read-only work, apply migrations from the pipeline rather than at application start-up, and switch to hand-written SQL through Dapper wherever that reads more plainly.

Staying on supported releases

Every .NET release carries a fixed end-of-support date. We hand over with that date and the steps to move up written down, so the next upgrade is routine maintenance rather than a project of its own.

FAQ

Questions to resolve before the build.

01Can you move our .NET Framework app to modern .NET?

Yes. Class libraries and services usually move with moderate effort. Web Forms pages and WCF server code need rewriting, so for large web apps we migrate route by route behind a proxy rather than all at once.

02Which .NET version should we use?

For most production systems, the current LTS release. STS releases suit teams who are happy to upgrade every year; we record the support end date either way.

03Do .NET apps have to run on Windows?

No. Modern .NET runs on Linux and in containers, which is often cheaper to host. Some older dependencies are Windows-only, and we flag them during the review.

04Do you build Blazor front ends?

Yes, when a team wants to stay in C# across the stack. For public-facing sites with heavy interactivity we also weigh a JavaScript front end.

Primary sources

References behind this page

Dated official documentation, standards, and research that support the factual claims on this page.

  1. 01
  2. 02

How to read this page

Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.

Next decision

Turn the brief into an accepted product scope.

Define outcomes, constraints, evidence, rights and handover before delivery begins.

Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.