Browse categories
English
$
USD
Connect to your AI
I will migrate your dot net framework app to dot net 10
Nikola R
About this gig
Your app still runs on .NET Framework, and every new library or security update makes it harder to keep alive. I move projects like that to .NET 10 step by step, so the app keeps working the whole way.
I know both sides. At my day job I maintain a shared C# library that targets .NET Framework 4.8.1 and .NET 10 at the same time, and I've fixed the runtime differences between the two that only showed up in production.
What I do:
- go through the solution and list what blocks the upgrade (packages, System.Web, WCF, config)
- move libraries to SDK-style projects, multi-targeted where it helps
- port ASP.NET MVC and Web API code to ASP.NET Core
- replace dead NuGet packages and keep EF6 working, or move to EF Core where it pays off
- keep the build and tests green after every step
You get a branch to review and a short report: what changed, what I left for later and why.
Send me the repository or a zip first. I'll tell you how big the job really is before you order.
Get to know Nikola R
Nikola R
Senior backend developer, APIs and n8n automation
- FromSerbia
- Member sinceOct 2026
Languages
English, Serbian
I've been writing C# for over six years, mostly on the backend. Right now I work on a smart-metering platform: .NET 10 services that talk over Kafka, with SQL Server and Cassandra behind them. Before that I built Azure backend services for a tax platform, and spent four years on a logistics company's TMS, ERP and CRM (ASP.NET Core, Angular, SQL Server). I started in 2018 in application support.
On Fiverr I take on API work, bug fixes in existing .NET apps, integrations and n8n automations. I find the cause before I change code, and I explain what I changed in plain words.
My Portfolio
Other Software Development Services I Offer
FAQ
Do you upgrade everything in one go?
No. I split the work so the app builds and runs after every step. You can stop at any point and still have something that works.
What about Web Forms or WCF?
Neither runs on .NET 10 as is. I lay out the options first (keep that part on .NET Framework, rewrite it, or use CoreWCF for services) and you decide before I start.
Does my database code have to change?
Not right away. EF6 runs on modern .NET, so the data layer can stay as it is. I suggest EF Core only where it's worth the effort.
Do you need access to production?
No. The code and a way to run it locally are enough. A test database helps.
Can we talk before I order?
Yes. Send the repository or a short description and I'll reply with what I see and a rough estimate.
