What we do
Tools
Industries
Department
How we workLet's talk →
Home/.NET Developer
.NET Development

Hiring a .NET Developer for an App Your Windows Servers Have Run for Years

Most .NET work isn't a blank page. It's an internal portal, an API other systems call, or a Windows service that shifts files overnight. It signs people in through Active Directory, keeps its data in SQL Server, and expects a dozen things from the server it's installed on that nobody wrote down. That second list is usually the bigger part of the job.

Which .NET is it on?

Open the project file. TargetFrameworkVersion set to v4.something, or a TargetFramework of net48, means .NET Framework. A TargetFramework like net6.0, net8.0 or net9.0 means modern .NET.

Solution Explorer Project Edit Project File

On .NET 8 or .NET 9? Both reached end of support on 10 November 2026, so they no longer get security patches. .NET 10 is the current long-term support release, covered until November 2028.

On .NET Framework 4.8 or 4.8.1? There's no cliff on the same date. 4.8.1 is the final Framework version and it's supported as part of Windows. The catch is that it won't get new features, and the Windows servers it lives on have their own end dates.

What the app is built from decides where it can go

A .NET app is rarely one thing. Most older solutions mix two or three of these, and each part moves on its own terms.

Built on Where it can go Watch for
ASP.NET Web Forms (.aspx pages) Nowhere directly. Web Forms isn't in modern .NET, so it stays on Framework 4.8.1 or gets rebuilt screen by screen in Razor Pages, MVC or Blazor Business rules sitting inside button-click handlers in the code-behind. They have to be pulled out before any page can be rebuilt.
ASP.NET MVC 5 or Web API 2 ASP.NET Core on .NET 10, with controllers and views reworked rather than rewritten Code that reaches for HttpContext.Current or anything in System.Web. Sign-in and permissions get set up again, not copied.
WCF services CoreWCF for the server side, or a REST or gRPC API in its place Who calls it. Other internal apps may talk SOAP to this service and need to keep working on the day it moves.
Windows service or scheduled console app A .NET 10 Worker Service, usually the easiest part to move The account it runs as, and the file shares and folders that account can reach today.
WinForms or WPF desktop app Modern .NET on Windows Third-party control libraries. Each one needs a version built for modern .NET, and some vendors stopped at Framework.
Already on .NET 8 or 9 Retarget to .NET 10, mostly package updates and a full test pass Libraries pinned to an old major version. Those are where the breaking changes hide, not in the runtime itself.

What a .NET app quietly expects from its old server

None of this is in the C#. It's in IIS settings, SQL Server and Active Directory, and it's why an app that tests fine falls over on cutover day.

Sign-in that only worked because the server was on the domain

How you'll know: On the new host, staff get a password prompt they never saw before, or a 401 on every page.

Fix: Set Windows authentication up for the new host, or move sign-in to Microsoft Entra ID with the same AD groups mapped to the same roles. List every group the app checks first.

SQL Server access through the app pool identity

How you'll know: The log shows Login failed for user 'DOMAIN\SERVER#x27;. The old server's machine account had database rights, and the new one doesn't.

Fix: Give the app its own service account, or a managed identity if it moves to Azure, with exactly the rights the old one had. Not more.

Work that lives in SQL Server Agent and stored procedures

How you'll know: The app moved fine, but the overnight totals or the 6am export stopped appearing.

Fix: List every Agent job and stored procedure the app relies on. Keep them where they are on purpose, or bring them into the app, but don't find out by losing a day's numbers.

Settings encrypted with the old machine

How you'll know: The app starts on the new server and can't read its own connection strings.

Fix: Config sections encrypted with the machine's own key only open on that machine. Decrypt them on the old server, then keep secrets in the new host's settings or a key vault.

COM components and DLLs registered on one box

How you'll know: A report, a PDF export or a label print works on the old server and nowhere else.

Fix: Find each registered component the app loads and decide: replace it, keep it on a Windows host, or wrap it in a small service the rest can call.

Let's talk

A .NET app that keeps its logins and its data when it moves

n-frames takes over .NET applications, writes down everything they lean on in Active Directory, SQL Server and Windows, and then moves them to .NET 10 or keeps them safely on Framework 4.8.1, whichever the code supports. Quoting the .NET move costs nothing.

Quote the .NET 10 move →

Questions people ask

Do you work with existing .NET systems, or only new builds?

Both. Taking over an existing one is as common as a new build. For an app that's already running, the first thing n-frames hands back is a written map of what it depends on outside its own code: which AD groups gate which screens, which SQL Server jobs it expects to have run overnight, which shares and services it calls. A new feature or a move to .NET 10 is planned from that map.

Does this need to integrate with the Active Directory or SQL Server we already run?

Almost always, and it shapes the work more than the code does. We build to the setup your IT team already has: the same AD groups decide who sees what, the same SQL Server holds the data, and if identity has moved to Microsoft Entra ID, sign-in goes through that. If the app moves to Azure, it connects under a managed identity rather than a password in a config file.

Won't a freelance .NET developer just be cheaper?

Per hour, possibly. On a .NET job the expensive mistake isn't slow code, it's the dependency nobody listed: a domain login, an Agent job, a COM component registered on one server. Missing one shows up as an outage after cutover, not in testing. Compare quotes on whether each one names those dependencies and says how they'll be handled, not on the rate.

No strings attached on the free quote?

None. We need read access to the solution, or an hour with whoever knows it, plus a list of the servers it runs on. The quote is free, and it counts the licensing choices, such as the SQL Server edition or Azure hosting, not just the build.

Do we have to move off .NET Framework 4.8?

Not by a deadline. Framework 4.8.1 is supported as long as the Windows version under it is. The reasons to move are practical ones: new libraries and Azure services target modern .NET first, Web Forms skills are getting harder to find, and the old Windows Server will need replacing at some point anyway.

What's the difference between a .NET developer and a C# developer?

C# is the language. .NET is the platform it runs on, plus ASP.NET, Entity Framework and the rest. Someone searching for a .NET developer usually has a business app on the Microsoft stack; a C# developer search is as often about a desktop tool or a Unity game.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.