.NET Developer for Hire — C#, ASP.NET Core 10, MAUI, Azure

What I build as a .NET developer

In business terms: if your company runs on Microsoft — Windows servers, Microsoft 365, Power BI, Dynamics, SQL Server, Active Directory / Entra ID — then your custom software probably belongs in the same ecosystem. I build the C# back-end APIs, the .NET MAUI desktop and mobile clients, and the Azure integrations that fit inside a Microsoft-shop enterprise without forcing your IT team to support a second platform. The technical breakdown:

• ASP.NET Core 10 web APIs and applications. The back-end services that power web and mobile apps — REST or gRPC, with the same audit trail, authorization model, and test coverage you expect from a Microsoft-supported framework. C# 13, ASP.NET Core 10, Entity Framework Core, Minimal APIs, FluentValidation, xUnit / NUnit test suites.
• .NET MAUI desktop and mobile clients. One C# codebase that ships to Windows desktop, macOS, iOS, and Android — without the React Native / Flutter learning curve for your in-house .NET team. MAUI for cross-platform UI, MVVM Toolkit for state, MAUI Community Toolkit for the gaps.
• Microsoft Entra ID / Azure AD integration. Single sign-on against your existing corporate directory, role-based access, conditional-access policies — the identity layer Microsoft-shop enterprises already trust. Microsoft.Identity.Web, MSAL, Graph SDK.
• Azure deployments and DevOps. The cloud infrastructure to run your .NET app — App Service, Container Apps, AKS, Functions, plus the GitHub Actions or Azure DevOps pipelines that ship it. Bicep or Terraform for infra-as-code, App Insights for monitoring.
• SQL Server, PostgreSQL, Cosmos integration. Database design and Entity Framework Core data access for the systems your business actually runs on. Migrations, query tuning, indexing strategy, and the audit logging compliance buyers expect.

Why a Microsoft-shop enterprise hires me

Most mid-market accounting, logistics, financial-services, and B2B companies in Texas run on Microsoft. Their IT team supports Windows servers and Azure. Their finance team runs Dynamics. Their sales team runs Outlook + Teams. When that company needs custom software, the lowest-friction answer is software that fits inside the Microsoft stack — same identity provider, same monitoring, same deploy story. I bring senior .NET experience (C# since the early 2000s, .NET Framework through .NET 10), single-principal accountability, and the discipline of a 25-year computer-science background. The engineer in the scoping call is the engineer writing the code.

.NET 10 — what changed for buyers

.NET 10 (released November 2025) is the current long-term-support (LTS) release. For buyers, the practical effect is faster runtime performance, native AOT compilation for smaller deploys, better C# 13 ergonomics for the team maintaining the code, and a longer support window than the .NET 8 baseline. New builds I take ship on .NET 10 unless there is a hard constraint forcing an older target.

How a .NET engagement is scoped

Same disciplined shape as my Laravel and PHP engagements: scoping conversation (free, 30 minutes), written specification (1–2 weeks, paid), two-week sprints with a working demo at the end of each, xUnit / NUnit tests written alongside features, handover with deployment runbook and 30-day post-launch support window. The difference for .NET is the deploy target: Azure App Service or Container Apps for most engagements, on-prem IIS for buyers with on-prem requirements, MAUI sideload + Microsoft Store for desktop and mobile.

.NET and AI — where they meet

Most of my AI engagements have a .NET surface somewhere: a C# admin tool that exposes the AI workflow to operations staff, an ASP.NET Core API in front of a self-hosted LLM, or a MAUI desktop client that lets domain experts review AI outputs offline. The AI developer page has the full AI scope; this page covers the .NET surface that ships alongside it.