.NET development services
We provide .NET development services for companies building transactional business platforms. We design and build new systems, move .NET Framework estates onto current .NET, and own the runtime and hosting decisions behind services, workers and desktop software.
01Capabilities
What we build with .NET
.NET provides application runtimes and libraries. Our custom software development includes platform architecture; our ASP.NET page covers web applications and our C# page covers language-level work.
- Platforms
Business platforms built from the ground up
Order management, dispatch, service and back-office platforms sit behind our logistics and transportation work and our automotive builds. We design the business rules and state transitions for systems your developers can keep changing. We work under an ISO 27001:2022 certified information-security management system.
- Workers
Services, workers and scheduled processing
We build queue consumers and integration daemons, including import and reconciliation jobs. We design Windows services and console processing around their hosting model, cancellation and restart behaviour.
- Integration
Integration layers between business systems
We connect ERPs, warehouse systems and payment providers, plus monitoring hardware in healthcare. We design idempotency, retries and reconciliation for repeated or interrupted exchanges through our platforms and integration work.
- Migration
Moving .NET Framework estates onto current .NET
We assess target frameworks, hosting and package compatibility to decide which services, desktop software and shared libraries to retarget or replace. Route-by-route web migration sits on our ASP.NET page; the platform work is part of legacy modernization.
02Case studies
.NET in production
Match your platform requirements to these .NET builds and migrations.
See all case studies
LogisticsCustom software for a US moving companyAn end-to-end SaaS platform for managing household moves and every business operation of a logistics company.Built from scratchAn end-to-end SaaS for household moves and the operations behind them- ModernizationRewriting and migrating a legacy platform onto .NET Core (Global On Media)unicrew rewrote Global On Media's codebase using .NET Core, React and Stencil.js and migrated its servers in the same engagement.
Knowledge ManagementSaaS for Digital ResearchA SaaS solution that helps knowledge workers streamline research work involving a substantial amount of information.
AutomotiveService Intelligence: App for vehicle maintenanceunicrew helped eAutoClub move Service Intelligence, an app that works out what service a vehicle needs from how it is actually used, from the desktop to a multitenant cloud platform.
SportSports app development for a triathlon associationunicrew engineers modernized the sports website and built a mobile app for better membership management and race planning.- HealthcareStabilizing and Scaling a Home Health Monitoring PlatformA U.S. consumer health tech company needed system stability and an experienced partner. unicrew stabilized the platform, optimized infrastructure costs, and delivered new features, becoming a long-term technology partner.
03Fit
How we decide .NET is the right call
We choose .NET around the system's business rules, existing integrations and operating environment. The recommendation also accounts for the developers who will maintain it.
| Your situation | What we recommend |
|---|---|
| A rule-heavy transactional system built around a Microsoft estate | Use .NETActive Directory, SQL Server and Windows operations inform the runtime and hosting choice. We design the platform around that estate and its maintenance path.Tell us what the system doesOr book a meeting |
| Web application routes, authentication or a Web Forms estate | ASP.NETOur ASP.NET page covers web framework architecture and migration. We scope that work around the routes, sign-in and framework dependencies.Go to the ASP.NET pageOr book a meeting |
| Language version, async correctness or a code-level refactor | C# language workOur C# page covers language versions, async correctness and code-level refactoring. We distinguish those changes from a runtime or hosting migration.Go to the C# pageOr book a meeting |
| A data processing or machine-learning pipeline | Use PythonWe recommend Python where its data and machine-learning libraries fit the workload, with the integration boundary defined alongside the business platform.Talk it through with an engineerOr book a meeting |
| An established JVM estate and a team that operates it | Java for that estateBuilding on Java preserves the established runtime, operations and maintenance knowledge. We assess the benefit of a platform change against those existing arrangements.Talk it through with an engineerOr book a meeting |
| A stable .NET Framework application on a supported version and host, with no required change blocked | Keep it patchedKeep the application patched while its framework version and Windows host remain supported. We plan a migration around a required capability, compatibility constraint or support change.Sanity-check that with usOr book a meeting |
On .NET, we give queue consumers and overnight jobs the same care as the web tier. Before we change how one runs, we make its failures visible and its restarts safe.
Oleksandr TrofimovChief Technology Officer, unicrew04Delivery
How a .NET Framework migration actually runs
A .NET Framework migration starts with a compatibility inventory. We agree which libraries and workloads can move, which require redesign, and how each cutover will be verified.
- Inventory the platform and buildWe inspect target frameworks across every project, the hosting model, third-party packages and their licence positions, and where the build is pinned. The inventory sets the scope for the migration.
- Assess framework and Windows dependenciesWe examine System.Web and Web Forms, server-side WCF, and Windows-specific APIs such as COM interop, GDI drawing, MSMQ and registry access. We assess current .NET compatibility and alternatives, including CoreWCF for WCF hosting, before deciding what to retain or redesign.
- Move shared libraries before hostsWe retarget shared domain and data libraries first, using multi-targeting where old and new runtimes need them during the transition. Hosts move once their dependencies are ready.
- Cut over one workload at a timeWe plan old and new hosts to run alongside each other, with a tested rollback path for each workload. We verify the change through QA and test automation before its cutover.
05Client voices
What these clients said
Site was migrated and re-written, the new system is much more stable, and performance highly improved. Excellent technological level. highly responsive and communicative. They are highly committed to the project and business goals.
Our website’s overall functionality has been improved both in frontend possibilities and user experience as well as backend aspects of website management and financial monitoring. These are not easily qualitfiable but there has been a net gain in available staff hours for alternative projects as a result of improved website abilities reducing workload.
We’re one of unicrew’s smaller clients, but they’re always incredibly quick to respond. When we have issues, they treat them as if they’re extremely important. We feel like we have a partner, and that’s been incredible. That’s why we’ll keep them on for as long as we can.
I’ve been impressed by their work ethic and how they put me as the customer first. They’re always ready to jump in and go the extra mile. They put great effort into communicating to ensure that tasks are updated in a timely manner. The team keeps us apprised of exactly what they’re working on.
Up until a year and a half ago, I handled all the development and support of our application myself and I needed help. I brought in Artelogic, and it was one of the best business decisions I’ve ever made.
06Stack
What we run alongside .NET
Use the linked stack pages when the decision is about a .NET system's language, web layer, data, hosting or interface.
07Questions
Questions we get about .NET work
Set the scope of your .NET engagement, from runtime compatibility to delivery ownership and pricing.
Yes. Our engineers can work within your team while owning the .NET platform and hosting decisions agreed for the engagement.
An architect outside the delivery team reviews those decisions, supported by our QA and test automation practice. A quality audit provides an assessment of the existing estate before you commit to a delivery scope.
Choose managed teams for ongoing .NET work with delivery coordination, or custom software development for an outcome we deliver.
.NET is the platform, C# is a language used on it, and ASP.NET is its web framework.
No. Current .NET runs on Linux and in containers; an application's dependencies determine whether it can move.
We check Windows-specific APIs and hosting requirements before choosing the target. COM interop, registry access and other Windows-bound components may still require Windows. Server-side WCF also needs a compatibility assessment, including whether CoreWCF fits.
.NET supports web applications, business platforms, background services and desktop software.
Our platform work includes new systems and migration from .NET Framework. For examples of public websites built on .NET, see our list of web resources built using .NET.
We start with a scoping call with an engineer.
For an existing estate, we ask for read access to the repository and build output. You receive a written recommendation covering the first work to undertake, what stays in place and where migration risk is concentrated.
Most engagements start within two to four weeks.
We quote .NET work against its scope using three engagement models.
- Time and materials: billed hourly and quoted per project.
- Fixed price: outcome based and quoted per project, once the scope is defined.
- Team extension: billed monthly per team member.
The model depends on how settled the scope is and whether we own a defined outcome or work inside your delivery process.
Build and evolve your .NET platform
Tell us what you want the system to do next. We will assess the platform and hosting decisions, identify what stays in place, and recommend the starting scope.