Working with C# and .NET?

C# app aging out or acting up? We take it on.

Most .NET work that reaches us is a line-of-business app that has been running quietly for years, built by somebody who is no longer around to answer questions about it. We read what is really there, write the missing notes down, and keep the thing earning its keep.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

application.log

still failing

What it is

C# and .NET at a glance

.NET is Microsoft's software framework for building and running applications, first released in 2002. The original edition, .NET Framework, was Windows-only and shipped as part of the operating system. From 2016 Microsoft rewrote it as the open-source, cross-platform .NET Core, and from 2020 unified both lines under the plain name .NET starting at version 5.

The primary languages are C#, F# and VB.NET, and the runtime powers web APIs with ASP.NET Core, desktop apps with WPF, WinForms and MAUI, background services, and serverless code on Azure Functions. A large share of corporate line-of-business software quietly sits on top of it.

Type
Software framework and runtime
First released
2002 for .NET Framework; 2016 for .NET Core
License
MIT for modern .NET; Framework ships as a Windows component
Maintained by
Microsoft and the .NET Foundation
Typically used for
Enterprise web apps, APIs, Windows desktop apps, internal tooling, Azure services

The honest version

C# and .NET pros and cons

No technology is all upside. This is where C# and .NET earns its place and where it tends to cause trouble.

Where C# and .NET is strong

  • A strong type systemThe compiler catches whole classes of bugs before the code ever runs, which is one reason .NET teams can keep large codebases moving for years.
  • Excellent tooling all roundVisual Studio, JetBrains Rider and the dotnet CLI cover debugging, profiling, refactoring and builds across every supported platform.
  • Fast and cross-platform nowSince .NET Core and the unified .NET 5 and later, the same code runs on Windows, Linux and macOS with serious throughput numbers behind it.
  • LINQ is first classQuerying objects, databases and XML uses one consistent syntax that reads close to the intent, which keeps data code tidy.
  • Async built in from the startasync and await were designed into the language, so network and database code stays readable instead of turning into callback soup.
  • A large enterprise footprintFinance, logistics, healthcare and government all run on it, which means hiring, hosting and vendor support are all easy to find.
  • Entity Framework for data accessEF Core maps your C# classes onto relational tables and handles migrations, which saves a great deal of hand-written SQL plumbing.
  • ASP.NET Core is production gradeIt is used by banks and major retailers, it performs very well under load, and it supports modern patterns such as minimal APIs out of the box.

Where C# and .NET bites

  • .NET Framework will not go away quicklyThe Windows-only line, topping out at 4.8.1, still runs a huge amount of production code, and it does not share NuGet packages or runtime with modern .NET.
  • The upgrade is not in placeMoving a Framework app to modern .NET is a porting job, not a patch, because the two runtimes sit side by side rather than one replacing the other.
  • WCF and Web Forms don't port cleanlyBoth were Framework-era technologies without direct replacements, so apps built on them need new designs rather than a straight recompile.
  • IIS tangles up Framework appsDeployment, app pool recycling and permissions are their own skill set, and when IIS misbehaves the app symptoms rarely match the real cause.
  • The version story confuses peopleFramework 4.8, .NET Core 3.1, and .NET 5, 6, 7 and 8 are easy to mix up on the wire, and installing the wrong SDK silently breaks builds.
  • Binary serialisation was deprecatedOld code that leaned on BinaryFormatter now throws at runtime on modern .NET, and replacing it means revisiting file formats and message contracts.

Sound familiar?

Common C# and .NET problems we fix

The C# and .NET problems that bring people to us, and what you have once each one is fixed.

.NET Framework 4.8 · EoS October 2026

The app is on .NET Framework and the clock is ticking

A working Framework app that nobody wants to touch, with a support deadline now visible on the calendar.

Ported to modern .NET on a plan

W3SVC event 1310

The ASP.NET app pool keeps crashing

Unhandled exceptions, memory climbing until IIS recycles the pool, and errors that only show up under real traffic.

Stable pool, root cause logged

last commit by: departed

The previous developer has moved on

Source code of unknown vintage, build steps that live in one person's head, and no written record of how to release a new version.

Builds reproducibly on a clean box

WCF service · no replacement

A WCF service still carries the integration

An older SOAP-style service that modern .NET does not support in the same way, holding up an upgrade.

Replaced with a supported stack

EF migration pending: 3

The database and the code are out of step

Entity Framework migrations that were never run, or a schema that was changed by hand and no longer matches the model.

Schema and code back in sync

NU1101 · 401 Unauthorized

The build does not work on a new machine

Private NuGet feeds with expired credentials, or an SDK version that is no longer installed anywhere.

New developer builds on day one

What we do

C# and .NET help, from rescue to upkeep

Call us for one failing release, or hand us the whole product.

Rescue
Apps that crash, builds that no longer run, releases that nobody dares to cut. We get them moving again first.
Framework to modern .NET
Planned migrations off .NET Framework 4.x onto .NET 8, rehearsed on a branch before anything ships.
Takeover
Inheriting a C# codebase from a previous developer, writing the missing notes, and getting it building on our own hardware.
Performance
Profiling ASP.NET Core and background services, fixing thread pool starvation, and making EF queries behave.
Integrations
Replacing WCF, wiring up Azure services, and tying .NET apps into the rest of your estate.
Managed Tech
Monitoring, patching, release engineering and a team to call, on an ongoing basis.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running C# and .NET alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

C# and .NET questions

Something else? Call+1 737 727 7327

Can you upgrade our .NET Framework app to modern .NET (.NET 8)?

Yes. We read the existing codebase first, flag the parts that will not port directly such as WCF, Web Forms or BinaryFormatter usage, and give you a plan with an estimate. The port itself runs on a branch alongside the live app until it passes the same tests.

What replaces WCF in modern .NET?

There is no single drop-in. For internal service-to-service calls we usually move to gRPC or ASP.NET Core minimal APIs. For SOAP clients that must keep talking to third parties, CoreWCF covers a useful subset. We pick the fit after reading your contracts.

Can you take over a C# line-of-business app from a previous developer?

Yes, and it is a large part of what we do. We take the source, reproduce the build on a clean machine, document how it releases, and leave you with a codebase a second person can safely touch.

Why is our ASP.NET app pool crashing?

Most often an unhandled exception on a background thread, a memory leak building up until IIS recycles the pool, or thread pool starvation from sync-over-async code. The event log and a profile usually tell us which within an hour or two.

Is .NET Framework still safe to use?

For now, yes, but it is the end of the line. Version 4.8 is the last supported Windows-only runtime and will go out of mainstream support in October 2026. New work should start on modern .NET, and existing Framework apps need a migration plan rather than a hope.

How much does .NET help cost?

Estimates are free. Tell us what the app does and where it hurts, and you get a price before any work begins.

Free estimate

.NET giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.