Skip to content
CompanyBenchCompanyBench

Hire .NET developers on contract: C#, ASP.NET Core and .NET upgrades

Hire a .NET developer on contract: C#, ASP.NET Core.NET 10 upgrades and Framework migrations. Vetted C2C shortlist of 3+ within 48 hours, one contract.

CompanyBench places .NET developers and .NET contractors with US companies on C2C terms, from the benches of US-based vendors and Indian IT vendors working offshore: C# and ASP.NET Core engineers for new builds.NET 10 upgrades and .NET Framework migrations. .NET rates are quoted per requirement. Within 48 hours of a confirmed requirement, at least 3 vetted, masked .NET profiles reach you, all under a single CompanyBench agreement.

Most ".NET contractor" searches in the US return job boards. This page is for the other side of that search: the hiring manager or IT lead who needs .NET capacity on contract. It covers where .NET and .NET Framework support stand this month, which .NET developer to ask for, what to test, and the mistakes that make .NET engagements run long. Other stacks are on the US technologies page.

Where .NET support stands in November 2026

Microsoft ships a new .NET version every November. Even-numbered versions are long-term support (LTS) releases with three years of free patches; odd-numbered versions are standard-term support (STS) with two years. Two versions just went out of support.

VersionTypeReleasedEnd of support
.NET 11STSNovember 10, 2026November 14, 2028
.NET 10LTSNovember 11, 2025November 14, 2028
.NET 9STSNovember 12, 2024Ended November 10, 2026
.NET 8LTSNovember 14, 2023Ended November 10, 2026
.NET Framework 4.8 and 4.8.1Windows component2019 and 2022Follows the Windows version it runs on
.NET Framework 4.6.2Windows componentAugust 2, 2016January 12, 2027
.NET Framework 3.5 SP1Windows componentNovember 18, 2008January 9, 2029
.NET Framework 4.5.2, 4.6, 4.6.1Windows component2014 to 2015Ended April 26, 2022

Source: Microsoft's .NET support policy and .NET Framework support policy. In practice: production on .NET 8 or 9 no longer gets security patches, and the target for most teams is .NET 10, the current LTS. The date most teams miss is January 12, 2027, when .NET Framework 4.6.2 leaves support; apps on 4.6.2 or 4.7.x can move to 4.8.1 as a short project, which keeps them on a supported runtime while a modern .NET migration is planned. .NET Framework 4.8.1 stays supported as long as the Windows version under it is.

Which .NET developer do you need?

".NET developer" covers very different jobs. Name the one you have, and the shortlist gets much better.

.NET workDay to dayPut in the requirement
Backend and APIsASP.NET Core Web APIs, minimal APIs, background workers, integrations with other systemsC#, ASP.NET Core, Entity Framework Core, SQL Server or PostgreSQL, OpenAPI, authentication with Entra ID or OAuth
Version upgrade.NET 8 or 9 to .NET 10: package updates, breaking changes, test fixes, CI and container imagesReading breaking-change notes, NuGet dependency work, a test suite they trust
Framework migrationA .NET Framework 4.x app moved to modern .NET, usually in stagesWCF, Web API 2, MVC 5, Windows services, plus the target stack; incremental migration habits
Full-stack .NETBlazor or an ASP.NET Core backend behind React or AngularBlazor Server or WebAssembly, or a JavaScript framework, plus the API layer
Azure .NETApp Service, Functions, Service Bus, Key Vault, deployment pipelinesAzure services by name, infrastructure as code, Azure DevOps or GitHub Actions
DesktopWPF and WinForms line-of-business apps, sometimes .NET MAUIWindows desktop work specifically; web .NET skills do not cover it

Name the kind of work. If the job is a Framework migration, say so up front. A strong ASP.NET Core developer who has never touched WCF or Web Forms code can lose weeks to the old app.

Moving off .NET Framework: what a migration contractor must know

Some .NET Framework features do not exist in modern .NET at all. Microsoft lists them on Learn. A migration lead should spot these in your codebase in the first week, because they decide how long the work takes:

  • AppDomains. Creating new app domains is not supported and won't be. Code isolation moves to separate processes or containers, and dynamic assembly loading moves to `AssemblyLoadContext`.
  • .NET Remoting. Not supported. Cross-process calls move to pipes or memory-mapped files; cross-machine calls move to HTTP or gRPC.
  • WCF server. Not part of modern .NET, but the CoreWCF packages let existing WCF services run on it. Ask whether the candidate has used CoreWCF or rewrote services as REST or gRPC, and why.
  • Windows Workflow Foundation. Not supported. The community CoreWF port is the usual route if you can't redesign the workflows.
  • Code access security. Gone as a security boundary. Sandboxing moves to the operating system: containers, separate accounts, least privilege.

A good migration plan moves shared libraries first (targeting .NET Standard or multi-targeting), keeps the old app running, and moves one service or project at a time behind tests. A plan that starts with "rewrite it" is usually a plan to miss the date.

What to test in a .NET interview

C# trivia is easy to memorize. These questions show whether someone has run .NET in production:

  • Async all the way down. Show a controller that calls `.Result` on a task. Ask what goes wrong under load. Look for thread-pool starvation and the fix: async from the controller to the database call.
  • Dependency injection lifetimes. Ask what happens when a singleton takes a scoped `DbContext` in its constructor. Candidates who have hit captive dependencies explain it fast.
  • EF Core performance. Give a query that loads a list and then touches a navigation property in a loop. Ask them to find the N+1 problem and fix it, and when they would reach for `AsNoTracking` or raw SQL.
  • An upgrade they did. Ask for the last version upgrade they ran: what broke, how they found it, how long it took. Vague answers mean they watched someone else do it.
  • Configuration and secrets. Ask where connection strings live in development, in CI and in production. The right answer never includes a committed `appsettings.json` with a password.
  • Testing. Ask how they test an API endpoint end to end with `WebApplicationFactory`, and what they would mock and what they would not.

For migration roles, add one more: give them a short list of packages and project types from your real solution and ask which ones they expect to cause trouble. You learn more from that than from a coding test.

.NET contractor rates

.NET rates are quoted per requirement, for offshore engineers from India and for US-based C2C developers. You see each person's hourly or monthly rate on the shortlist before you interview, there is no placement fee, and the rate is agreed upfront. What moves it:

  • Migration depth. Engineers who have moved large .NET Framework estates, including WCF and Windows services, cost more than API developers.
  • Azure and architecture. Leads who design the Azure footprint and review others' code sit above developers who build to a design.
  • Domain. Healthcare, insurance and banking work with audit and compliance requirements narrows the pool.
  • Hours and location. Full overlap with US business hours, US-based engineers and on-site days are priced separately from offshore work.

If you have a budget, put it in the requirement and we will tell you which seniority it buys.

How hiring a .NET developer works

  1. Send the requirement: the kind of .NET work, the .NET or .NET Framework version, database, Azure services, front end, the next three months of work, overlap hours, remote or on site, and length.
  2. We confirm it and agree a rate range, then route it to IT vendors whose benches include .NET developers on that version and stack.
  3. Within 48 hours at least 3 masked profiles reach you (initials, role, years, certifications, location, rate), each listing the .NET versions and the apps the developer has upgraded or built.
  4. CompanyBench books each interview call; no contact details are shared either way.
  5. You choose a developer. You contract with CompanyBench alone, and CompanyBench holds the back-to-back agreement with the developer's employer.
  6. The developer starts in your solution. Each month you approve the hours and pay one CompanyBench invoice; the vendor is paid by CompanyBench.

How we vet .NET developers

  • A government ID checked against the person on the profile.
  • A .NET assessment matched to the work: ASP.NET Core and EF Core for backend roles, Framework internals such as WCF and AppDomains for migration roles.
  • Proxy and deepfake interview screening, so the engineer you approve is the one in your repository.
  • Microsoft certifications verified when the profile lists them.
  • For .NET developers employed in India, a UAN check that rules out dual employment.
  • A background check completed before day one.

Example: a .NET Framework 4.6.2 app before January 2027

Example: a healthcare billing company runs an ASP.NET MVC 5 portal and two WCF services on .NET Framework 4.6.2, which leaves support on January 12, 2027. The requirement reads: one senior .NET developer with WCF and modern .NET migration experience, remote from India with four hours of overlap with Central time, nine months. Phase one: retarget to .NET Framework 4.8.1 and fix what breaks. Phase two: move shared libraries to .NET Standard, then the services to .NET 10 with CoreWCF or gRPC, one at a time. The shortlist shows three masked profiles with rates and the migrations each has done. The IT lead sends each candidate the project and package list, asks which items will cause trouble, picks one, and has the solution, database and Azure DevOps access ready for day one.

Mistakes US teams make hiring .NET contractors

  • Asking for ".NET" without a version. A .NET 10 API developer and a .NET Framework 4.8 WCF maintainer are different hires. Put the versions in the first line of the requirement.
  • Upgrading without tests. If the app has thin test coverage, make tests on the main flows the first task. Otherwise nobody can say whether the upgrade broke anything.
  • Staying on an unsupported version because it still runs. .NET 8 and 9 stopped getting patches on November 10, 2026. Auditors and security scanners will flag it.
  • Hiring a web developer for a desktop app. WPF and WinForms work needs people who have shipped Windows desktop software.
  • Big-bang rewrites. Migrate in stages behind working software. Ask every candidate how they would keep the old app shipping during the move.
  • No access on day one. .NET contractors need the solution, the database, Azure access and a working build on the first day. Waiting a week for VPN access is a common reason a contract starts slowly.

How the C2C arrangement works for a .NET hire

Your .NET developer stays on their IT vendor's payroll; the vendor contracts with CompanyBench, and CompanyBench contracts with you, so you run no payroll and receive one invoice. See the US hiring overview for the model and C2C, W2 and 1099 compared for how a C2C .NET contractor differs from a W2 hire. .NET teams on Azure often add Azure engineers; for another enterprise backend, see Java developers. Ready? Send a requirement.

Frequently asked questions

How much does it cost to hire a .NET developer?

Through CompanyBench.NET rates are quoted per requirement, for offshore developers from India and for US-based C2C developers. The rate depends on seniority, migration or Azure depth, domain and the hours you need covered. You see each person's hourly or monthly rate on the shortlist before you interview, and there is no placement fee.

Is .NET 8 still supported?

No. Microsoft ended support for .NET 8 and .NET 9 on November 10, 2026, so they no longer get security patches. .NET 10 is the current long-term support release, supported until November 14, 2028. Most teams on .NET 8 should plan the move to .NET 10, which is usually a contained upgrade if the app has tests.

Is .NET Framework 4.6.2 still supported?

Yes, until January 12, 2027, according to Microsoft's .NET Framework support policy. After that date it gets no security fixes. Moving to .NET Framework 4.8.1 is the short route, because 4.8.1 is supported for as long as the Windows version under it; moving to .NET 10 is the longer, better route for apps you plan to keep.

Is a .NET contractor W2, 1099 or C2C?

Through CompanyBench it is C2C. The developer stays on their own IT vendor's payroll, the vendor contracts with CompanyBench, and you contract with CompanyBench. You don't run payroll or benefits for the developer, and you get one invoice a month for approved timesheets.

Is CompanyBench a Microsoft .NET partner?

No. CompanyBench is not a Microsoft partner and does not resell Microsoft licenses or services. We supply contract .NET developers who work in your team and take direction from your leads. If you need a Microsoft partner for licensing or a fixed-scope project, use one; contract developers can still work alongside them.

Can an offshore .NET developer migrate our .NET Framework app?

Yes, if you hire for it. Ask for engineers who have moved Framework apps with WCF, Windows services or Web Forms to modern .NET, and give them the solution early so they can list the blockers. Offshore developers usually overlap with the US morning; agree the hours you need before the start.

How soon does a .NET shortlist arrive?

At least 3 masked .NET profiles with rates arrive within 48 hours of confirming the requirement. Start dates depend on each developer's notice and your onboarding. Have the solution, the database and Azure or Azure DevOps access ready before day one.

Tell us what you need

A vetted shortlist within 48 hours of confirming the requirement. No fees until someone starts.

What you need
How to reach you

We use these details only to respond to you. See our privacy policy.

Sources

Last reviewed November 22, 2026.

Our United States office

9300 John Hickman Pkwy, Suite 1101, Frisco TX 75035, United States