.NET when the business already lives on Microsoft
Successor work to the ASP.NET backends this firm was founded around: MVC sites, Web APIs, and the relational store they already trust.
We take .NET work when the system of record is already there — SQL Server, existing identity, a service the rest of the company calls. We do not recommend a rewrite onto a fashionable stack to make the staffing easier.
Typical .NET engagements
- ASP.NET Core APIs that other teams can version against.
- MVC or Razor apps that have to keep working while a piece is replaced.
- SQL Server work that is allowed to stay SQL Server.
When .NET is the wrong page
If the product is a greenfield consumer UI with no Microsoft estate, start on the React page. If the team is C# and the UI should stay C#, that is Blazor.
We will also say no to a “.NET modernization” that is really a rewrite with no users named. Name the API or the form that has to work on a date. That is a project. A slogan is not.