Services
.NET applications
Line-of-business .NET, changed by someone who will still answer after it ships.
Internal applications, integrations, and careful modernization. For firms whose operational software is a .NET system the current team did not write.
A change that still ships from one developer’s machine is not finished. Automated environment builds and repeatable deploys — Ansible, Terraform, GitHub Actions or GitLab CI — take the manual release toil out of the application project. They do not turn it into a platform team. See Build automation & IaC.
Who it is for
- A firm with an internal app for billing, staffing, cases, inventory, or the workflow nobody wants to say out loud.
- A codebase one contractor understands, and everyone else is afraid to open.
- A team that needs that app to speak to a CRM, a database, or a file the business already trusts.
What the work includes
C#, ASP.NET, and the screen that is stuck
The page the business complains about, and the C# or ASP.NET behind it, before anyone proposes a new platform. Entity Framework when the data access is already there and should stay understandable.
WebAPI and WCF
Services the rest of the stack can call: WebAPI for a newer front end, WCF where the integration is already a service contract. The failure has to be visible to an operator, not only to a log.
AngularJS modernization
A front end that can replace a screen the business has outgrown, scoped to that replacement. Not a rewrite of every internal tool because a framework is familiar.
A VB6 bridge, then a replacement
When a VB6 client is still the system of work, the first project is often a bridge into .NET and the web app beside it. Past automotive-aftermarket work at Fisher Auto Parts was that shape: VB6 integrated with the site, and an AngularJS and WebAPI path aimed at replacing the VB6 programs.
Handoff the in-house developer can use
Notes and a path through the change. A past lead at NRECA moved a mainframe-era application onto C#, WCF, and SQL Server. The point of that kind of project is a system the current team can run after the engagement ends.
How an engagement starts
A .NET engagement starts with the screen the business complains about and the code behind it. The deliverable is a smaller, explained change — or a sequenced plan if the system is too tangled for one pass. Past work has included Fisher Auto Parts, CFA Institute’s WCF and WebAPI services beside Siebel, and a short .NET lead at NRECA. None of those are current employers.
If .NET applications is the project, send a paragraph.
Name the system, what is stuck, and any date that already exists. That is enough to tell whether this practice is the right one.