.NET Development

What we do in the .NET ecosystem

• ASP.NET Core API + Web app builds for new SaaS and internal tooling
• Blazor Server and WebAssembly when the brief is .NET-only
• Azure architecture for .NET workloads — App Service, Functions, AKS, Service Bus, SQL
• Modernisation from .NET Framework 4.x / WebForms / WCF to ASP.NET Core 8/9
• Performance work — Entity Framework tuning, async patterns, caching strategies
• Integration with Microsoft 365, Dynamics 365, Power Platform APIs
• Microservices and event-driven systems on Service Bus, Event Grid, Event Hubs

The .NET Framework migration question

If you're still running .NET Framework 4.x in 2026, you're not alone — a large slice of Australian mid-market businesses still are. Microsoft has committed to indefinite support for 4.8, so technically nothing forces you to migrate. But you'll face increasing friction: new package versions stop supporting it, hiring becomes harder, and Microsoft's investment now goes entirely into modern .NET.

We use the YARP reverse-proxy strangler-fig pattern: stand up a new .NET 9 app alongside the legacy one, route specific URLs to the new app, migrate features one at a time. Old and new run in production together for months. Risk is contained per feature; rollback is a routing change.

How we approach .NET architecture

Vertical slice architecture, not Clean/Onion

For most SMB-scale apps we build, the layered Clean/Onion architecture adds ceremony without benefit. We default to vertical-slice (feature-folder) architecture with MediatR or minimal APIs — easier to onboard new developers, less code per feature, simpler to reason about.

EF Core by default, Dapper when measured

Entity Framework Core is fast enough for almost all SMB workloads we see. We use Dapper or raw SQL only when we measure an actual bottleneck — never preemptively.

Azure-first hosting

App Service for most workloads, Functions for event handlers, AKS only when we have a specific reason (multiple services that actually need orchestration, or complex networking). All data residency pinned to Australian regions.