End of support: November 10, 2026

Your .NET 8 and .NET 9 apps stop getting security patches on November 10, 2026.

I upgrade them to .NET 10, the current LTS release supported until November 2028, for a fixed price. You get a pull request with your own tests passing. No hourly billing and no mandatory calls.

Start with a US$190 audit Run the free check first

What happens if you stay on .NET 8 or 9

Your app keeps running. What stops is everything that keeps it safe to run:

No more security fixes. Microsoft ships runtime and ASP.NET Core patches every month on Patch Tuesday. After November 10, 2026, .NET 8 and .NET 9 get none.
No bug fixes and no Microsoft support for those versions.
Vulnerabilities found later stay open in your runtime, even when the fix exists for .NET 10.
Security scanners and audits commonly flag unsupported runtimes, which tends to surface in customer security reviews.
Azure Functions on the in-process model also reaches end of support on November 10, 2026, and .NET 10 only runs on the isolated worker model.

Sources: .NET Blog: .NET 8 and .NET 9 will reach End of Support on November 10, 2026 · .NET support policy · Breaking changes in .NET 10 · Azure Functions: migrate to the isolated worker model

Three fixed prices

Prices in USD. You know the full cost before anything starts.

1. Audit

US$190

Written report in 48 hours from access. One solution, up to 30 projects.

Every project, its target framework and what blocks .NET 10
NuGet packages without .NET 10 support or with known vulnerabilities
Breaking changes that touch your code, with file references
Docker images, CI pipelines and Azure Functions model
Effort estimate and the upgrade size that fits

The US$190 is credited in full if you order the upgrade within 30 days.

Buy the audit

2. Upgrade one app

from US$590

Pull request with your tests green.

Target framework, SDK and global.json moved to .NET 10
NuGet packages updated to compatible versions
Build errors and breaking changes fixed
Dockerfiles and CI pipeline SDK versions updated
Upgrade notes: what changed and what to watch on deploy
14 days of fixes for anything the upgrade caused

Small, US$590 Medium, US$990 Large, US$1,490

3. Keep Current

US$290 / month per app

Stay patched without thinking about it.

Monthly .NET servicing update after Patch Tuesday, as a PR
Dependency updates (patch and minor), majors flagged and planned
CVE monitoring on your packages, fix PR when one applies
Next LTS upgrade (.NET 12, expected November 2027) included after 6 paid months
Cancel any month

For Small and Medium apps already on .NET 10. Larger apps: ask for a quote.

Upgrade sizes

Size	Price	Projects	Code lines	Delivery
Small	US$590	up to 5	20k	5 days
Medium	US$990	up to 15	80k	10 days
Large	US$1,490	up to 30	200k	15 days

Projects in the solution and lines of C#/Razor code. Delivery in business days from access. Generated code and test projects do not count toward the line limit. If your app turns out bigger than the size you bought, I tell you before starting and you choose: pay the difference or get a full refund.

Not included in any plan

Deploying to your servers or touching production
Applying database migrations (I generate them, you apply them)
New features or refactoring beyond what the upgrade needs
Paid third-party component licenses (Telerik, DevExpress and similar)

Quoted separately

.NET Framework 4.x to .NET 10 migrations
Web Forms, WCF server and Xamarin apps
Solutions above the Large limits
Apps on .NET 6 or 7 with many outdated packages (the audit tells you)

How it works

Everything happens in writing, on your schedule. A 15-minute call is available if you want one, never required.

Pick a plan and pay. Not sure about the size? Buy the audit, or run the free tool below and send me the output.
Give read-only access. Add a read-only collaborator on GitHub, Azure DevOps or GitLab, or send a zip. No production credentials, no secrets.
The work gets done. A set of AI coding agents does the analysis, the upgrade and the test runs. I review every change and sign off before you see it.
You get a pull request. With upgrade notes and the test results. You review, merge and deploy when it suits you. Without write access, you get a patch file.

When the job is done

The upgrade is accepted when your solution builds on .NET 10 and your existing tests pass with dotnet test. Tests that already failed before the upgrade are listed in the notes and stay out of scope.

No automated tests? We agree on a short smoke checklist before I start, and that becomes the acceptance criterion.

I never touch production. No deploys, no production databases, no infrastructure changes.

Guarantee

If the audit is not useful to you, tell me within 7 days of delivery and I refund it. No questions, no form.

If your app does not fit the upgrade size you bought, you hear it from me before any work starts, with the option of a full refund.

Free first step: check your solution yourself

Net10Check is a free command-line tool. Run it in the folder of your solution and it lists the projects, packages and settings that will need work to reach .NET 10, including packages that have no .NET 10 release yet. Nothing is uploaded anywhere.

dotnet tool install -g Net10Check
net10-check

If the report is short, you can probably do the upgrade in-house. If it is long, send it to me and I will tell you, for free, which size fits.

On Umbraco 13? It loses support on December 14, 2026

Umbraco 13 is the last version on .NET 8 with the old AngularJS backoffice. Moving to Umbraco 17 LTS (supported until November 2028) means a new backoffice, so custom dashboards and property editors built in AngularJS have to be rebuilt, and some community packages still have no version for 17.

Umbraco17Check is a free command-line tool that shows, for your site, which packages already support Umbraco 17, which ones block the upgrade, how much AngularJS backoffice code you have and which content model features need migrating. It runs locally and uploads nothing.

dotnet tool install -g Umbraco17Check
umbraco17-check

Send me the report and I will quote the upgrade to Umbraco 17 at a fixed price. Message me on Upwork.

Also at a fixed price

Azure Service Bus SDK migration: the old SDKs are retired on September 30, 2026.
Azure Functions in-process to isolated worker: in-process ends support on November 10, 2026.
Umbraco 13 to 17 upgrade: Umbraco 13 reaches end of life on December 14, 2026.

FAQ

Do you handle Blazor apps?

Yes, Blazor Server, WebAssembly and the Blazor Web App template. The ASP.NET Core 10 breaking changes (for example the obsolete WebHostBuilder and Razor runtime compilation) are part of the upgrade.

What about EF Core?

EF Core is upgraded to 10 along with the app. I check the EF Core 10 breaking changes against your model, such as the new JSON column type on Azure SQL and the new translation of parameterized collections. If the model changes, I generate the migration and you decide when to apply it.

We use Azure Functions.

Isolated worker apps are upgraded like any other project. In-process apps have to move to the isolated worker model to run on .NET 10, and that code migration is included. Switching the function app in Azure to the isolated runtime is a deployment step, so you do it; the upgrade notes explain how, ideally through a staging slot. Each function app counts as one project for sizing.

Our app is on .NET Framework 4.x.

That is a different job with a different risk profile. Send me the Net10Check report or buy the audit and I will quote it separately.

Will you sign an NDA?

Yes. Send yours before sharing access and I sign it.

How do you handle our code?

Read-only access only, no production secrets needed. The code is worked on in a private environment and I delete my working copy whenever you ask. The work uses AI coding tools under my review; if your policy restricts that, say so before buying and I will tell you plainly whether I can take the job.

Why fixed prices and not hourly?

You should know the cost before approving the work. The audit tells you the size, the size sets the price.

Who is behind this

I am Mauricio Acuña, a .NET developer with 13 years of production work in C#, ASP.NET and EF Core (and Blazor more recently), the last three remote with US teams. I have led teams of up to 8 developers. I work from Argentina (GMT-3, overlapping US business hours) and write in English.

I use a set of AI coding agents to do the repetitive part of an upgrade: scanning, package bumps, build fixes and test runs. I review every change and I am the one who signs off on your pull request.

Upwork