Hire .NET Developers
A great deal of business software still runs on .NET Framework: Web Forms intranets, WinForms desktop programs on every till or workstation, WCF services that other systems depend on. It works, it is supported by Microsoft as part of Windows, and it cannot simply be switched off. It needs developers who know both the old platform and the new one.
That is the profile we propose for .NET work. The developer connects to your source control and your ticket system and is directed by you. PWTECH handles employment and continuity in the background.
Kinds of .NET work we take, old and new
Some clients want an old application kept alive. Others want to leave it behind. Both are legitimate, and the six jobs below cover each case.
Maintaining .NET Framework applications
Fixes and new features in ASP.NET MVC 5, Web API 2, Web Forms and Windows Services running on Framework 4.x. We work inside the existing structure and do not force a rewrite on a system that only needs a change.
WinForms and WPF desktop software
New screens, reports, printing, device integration and installer updates. Desktop projects can also be retargeted to current .NET while remaining Windows applications, which brings newer language features and better performance.
Web Forms replacement
Web Forms has no counterpart in modern .NET, so pages have to be rebuilt in Razor Pages, MVC or Blazor. We extract the logic from code-behind files into plain classes first, then replace the pages in groups while the old site stays online.
Incremental migration to current .NET
A new ASP.NET Core application is placed in front of the old one and forwards any route it does not yet handle. Routes are moved across one at a time. Shared libraries are retargeted to .NET Standard 2.0 so both sides can use them during the transition.
WCF and SOAP services
Keeping existing contracts alive for callers that cannot change, porting services to CoreWCF, or replacing them with REST or gRPC where every consumer is under your control.
Entity Framework 6 and SQL Server
Tuning generated queries, replacing EDMX models with code-based mapping, reviewing stored procedures, and planning the move from EF6 to EF Core, which behaves differently in several areas.
Microsoft stack, from Framework 4.8 to current .NET
A migration developer needs to be fluent on both sides of the divide. These are the technologies involved.
- Languages
- C#VB.NETT-SQL
- Web (Framework)
- ASP.NET Web FormsASP.NET MVC 5Web API 2WCFIIS
- Desktop
- Windows FormsWPFWindows ServicesClickOnce
- Data
- SQL ServerEntity Framework 6ADO.NETDapperSSRS
- Migration targets
- ASP.NET CoreEF CoreBlazorCoreWCFYARP.NET Standard 2.0
- Build and release
- Visual StudioMSBuildNuGetAzure DevOpsNUnitxUnit
How much .NET experience the task calls for
On legacy systems, experience counts for more than usual, because much of the knowledge is about how things were done in earlier versions and why.
Junior
Makes defined changes to forms, pages, controllers and stored procedures. Can debug in Visual Studio and follow existing code. Needs supervision around view state, threading in desktop applications and anything touching deployment.
Choose when: the changes are routine and an experienced .NET developer reviews them.
Mid-level
Owns features across the user interface, business layer and database. Understands the page life cycle in Web Forms and data binding in WinForms or WPF. Can retarget a class library and resolve the package conflicts that follow.
Choose when: the application is stable and you need regular enhancements and fixes.
Senior
Plans a migration: which projects move first, which dependencies block the way, what can be shared and what must be rewritten. Has worked on both Framework and current .NET and can estimate the difference honestly.
Choose when: you are deciding whether and how to migrate, or the system is critical and poorly documented.
Bringing a .NET developer into your team
Describe what you have
The Framework version, project types in the solution, database and hosting. Tell us whether the aim is maintenance, migration or both.
Speak to the developer proposed
We name one engineer whose background matches your platform. You question them directly. Another candidate is available on request.
Agree an initial task
Choose a fix or a small feature. On migration projects, a dependency report on the solution makes a useful first deliverable.
Carry on in a fixed rhythm
The work is managed in your tools, such as Azure DevOps or Jira. A weekly summary sets out what was completed and what needs your input. You are invoiced monthly.
.NET developer rate card
Our rates are published. Pick the role and move the sliders for an indicative budget.
Rate card
| Role | Hourly | Monthly* |
|---|---|---|
| Frontend / WordPress | AED 110 | AED 17,600 |
| Backend / API | AED 118 | AED 18,880 |
| Full-stack | AED 129 | AED 20,640 |
| Mobile (React Native / Flutter) | AED 129 | AED 20,640 |
| DevOps / Cloud | AED 147 | AED 23,520 |
| AI / Automation engineer | AED 165 | AED 26,400 |
| QA / Test engineer | AED 92 | AED 14,720 |
| UI / UX design | AED 103 | AED 16,480 |
*160 hrs/month full-time. Rates are indicative for planning, in UAE dirhams (converted from our US-dollar rates at the fixed peg of 3.6725), before VAT where applicable, and depend on seniority, contract length and timezone overlap. Longer engagements and multi-role teams are discounted — ask.
Does a remote .NET developer suit your system?
We are a good choice when
- You depend on a .NET Framework application and the original developers have gone.
- You plan to migrate in stages and need someone to do the work between releases.
- You have desktop software in daily use that still needs new features.
- You are a software vendor and need more .NET developers on your product.
Look elsewhere when
- You want a full rewrite quoted at a fixed price before anyone has examined the code.
- The only task is a brief one-time correction.
- The source code has been lost and only compiled assemblies remain. Recovery is possible but is a separate, slower exercise.
- Staff must be physically present at your location.
Legacy .NET and migration: common questions
Is .NET Framework still supported?
Yes. Framework 4.8 and 4.8.1 are components of Windows and are supported for as long as the Windows version they ship with. They receive security and reliability fixes but no new features. There is no forced deadline, which allows a migration to be planned calmly.
Can Web Forms be converted automatically?
No. There is no tool that turns Web Forms pages into modern equivalents, because the page model, view state and server controls do not exist in current .NET. The business logic can be reused; the pages are rebuilt.
Must we migrate everything at once?
No, and we advise against it. The incremental approach keeps the old application serving requests while routes are moved across individually, so the business is never waiting on one large release.
We have VB.NET code. Is that a problem?
Not for maintenance. VB.NET runs on current .NET for class libraries, console and Windows desktop projects, but it is not supported for ASP.NET Core web projects. If the web layer is in VB.NET, that layer would be rewritten in C# during a migration.
Who owns the code and the migration documents?
You own both. Everything is checked into your repository, and the agreement confirms ownership and confidentiality before work starts.
How do we bring the engagement to a close?
Engagements are month to month. Inform us before the coming month begins. The developer then hands over current work together with written notes.
Tell us which .NET system needs attention
Let us know what the application does, which .NET version it targets, and whether you want it maintained or migrated. Our answer comes within one business day.