APIs for field apps
One API serves a web dashboard and a mobile app that works offline and syncs later.
Backend
ASP.NET Core development services for APIs that field apps depend on
The API layer behind a React dashboard and a .NET MAUI field app: scheduling, validation rules and certificates on Azure SQL. For the whole .NET stack, see our .NET page.
1Published build, the Digital Testing Platform
70%Faster reporting cycle on that build
13 Dec 2022.NET Core 3.1 end of support
14 Nov 2028.NET 10 LTS end of support
What we build
What we build with ASP.NET Core
Validation rules
Automated thresholds and exception workflows on every test result.
Certificate generation
Instant PDF with GPS, timestamps and readings, ready for audit.
Upgrades from .NET Core 3.1
Apps on a runtime that lost support in 2022, moved to .NET 10.
Architecture
Inside the API layer
What an ASP.NET Core API carries
Clients
React web dashboardJobs, clients, Test Map
.NET MAUI field appTests, photos, Bluetooth
ASP.NET Core API
SchedulingAssign engineers, notify
Validation rulesThresholds and exceptions
CertificatesPDF with GPS and readings
Storage
Azure SQLJobs and results
Azure Blob StoragePhotos and PDFs
From the Digital Testing Platform for work-at-height anchor and torque checks.
Versions
Leave .NET Core 3.1 behind
From an unsupported runtime to a supported one
Ended 13 Dec 2022
.NET Core 3.1
- Microsoft ended servicing and technical support
- Apps keep running without security fixes
Supported to 14 Nov 2028
.NET 10
- Long-term support release
- Microsoft dropped Core from the runtime name with .NET 5
Source: Microsoft, .NET Core 3.1 end of support notice and .NET support policy, checked 30 October 2026.
Builds
The ASP.NET Core build we can show you
Statutory inspection, United Kingdom
Work-at-height anchor and torque platform
ASP.NET Core and Azure SQL behind a React dashboard and a .NET MAUI field app, fixed price per phase with a 60-day warranty.
70%Faster reporting cycle
Fit check
When ASP.NET Core is the right call
Pick ASP.NET Core when
- A web and a mobile client need one API
- Results must pass rules and produce a signed record
- Your team already runs .NET and Azure
Look elsewhere when
- A static site with no back end
- The workload is mostly machine learning, where Python fits better
- You need many published ASP.NET Core builds to compare
Explore
Same job, other tools
Where we used it
See also: for the wider .NET platform, including desktop and mobile, read the .NET page.
Stack
What ASP.NET Core usually ships with
AzureReact
Xamarin
Docker
Angular
AWSFAQs
What buyers ask first
Is .NET Core the same as ASP.NET Core?
No. .NET Core was the cross-platform runtime, and Microsoft dropped Core from its name with .NET 5. ASP.NET Core is the web framework that runs on it and kept its name.
Is .NET Core 3.1 still supported?
No. Microsoft ended support for .NET Core 3.1 on 13 December 2022. Apps keep running, but they receive no security fixes.
Which version should a new API target?
.NET 10, a long-term support release with end of support on 14 November 2028.
Who owns the code and the cloud accounts?
You do, from the first commit. Repositories and cloud accounts stay in your name.
Tell us what your API has to enforce
Thirty minutes on your rules, your clients and your runtime. No sales pitch.