.NET Application Support & Upgrades
for Australian businesses.

.NET Framework (4.x) is in maintenance mode. Microsoft will not add new features. .NET 8 and 9 (the modern, cross-platform .NET) are where all the investment is going. Performance is dramatically better, cross-platform support, better cloud deployment, and active development.

We migrate ASP.NET MVC and Web API applications from .NET Framework to .NET 8 or 9. This involves updating project files to SDK-style, migrating NuGet packages, replacing System.Web dependencies, updating authentication, and resolving breaking changes.

Not every .NET Framework application can be migrated incrementally. We assess whether YARP (reverse proxy) sidecar migration, strangler fig pattern, or full rebuild is the best approach for your codebase.

Already on .NET Core or .NET 5/6/7? Version upgrades to .NET 8 or 9 are usually straightforward, but still require testing. Breaking changes between versions, deprecated APIs, and updated NuGet packages need attention.

.NET 6 LTS support ended November 2024. .NET 7 was a short-term release (already EOL). .NET 8 is the current LTS with support until November 2026. Keeping current means security patches and performance improvements.

We handle the upgrade, test everything, and deploy to staging before production. Entity Framework migrations, Identity changes, Minimal API updates, and Blazor component updates are all covered.

.NET applications with security vulnerabilities: outdated NuGet packages with CVEs, SQL injection via raw queries, XSS in Razor views, insecure authentication configuration, or CSRF protection gaps.

We run dependency audits (dotnet list package --vulnerable), static analysis, and manual code review. Vulnerabilities are prioritised by severity and fixed. NuGet packages updated to patched versions.

For applications on end-of-life .NET versions (.NET Core 2.1, 3.0, .NET 5, .NET 7), the most important security fix is the version upgrade itself. Microsoft does not patch EOL versions.

Monthly support plans for .NET applications. Bug fixes, security monitoring, NuGet dependency management, performance optimisation, and small feature requests. A developer who knows your codebase.

Proactive monitoring: uptime, error tracking (Sentry, Application Insights), performance metrics, and NuGet vulnerability scanning. Issues caught before your users notice. Monthly reports on application health.

Previous developer left? We take over .NET codebases. Audit the architecture, document the solution structure, set up CI/CD (Azure DevOps or GitHub Actions), and resume development. No judgement about the code, we just pick it up.

.NET applications running on on-premises Windows Server moved to Azure or AWS. App Service, Azure SQL, Azure AD integration, and managed services replace self-managed infrastructure.

IIS on a Windows Server in the office or a data centre replaced with Azure App Service or AWS Elastic Beanstalk. SQL Server on a VM replaced with Azure SQL Database or AWS RDS. File storage moved to Azure Blob or S3.

The cloud migration often happens alongside the .NET version upgrade. Moving from .NET Framework on IIS to .NET 8 on Azure App Service (Linux) is a common and well-trodden path.