TECHNICAL CASE STUDY · 2025
Licensing Modernisation
Connecting a legacy software-licensing system to modern .NET applications.
The case study focuses on the engineering problem without exposing licensing parameters, protocols or infrastructure.
- CONTEXT
- Legacy system modernisation
- ROLE
- Sole developer
- WHEN
- 2025
- STACK
- .NET 8 · ASP.NET Core · REST · SOAP
The problem
An existing .NET Framework software-licensing system needed to work with modern .NET applications while preserving compatibility with a legacy integration.
What I owned
- Migrated the legacy library from .NET Framework to .NET 8.
- Researched the unsupported SOAP integration and implemented a replacement compatibility layer.
- Designed an ASP.NET Core REST API with routes, DTOs, a service layer and five licensing operations.
- Solved the distinction between the REST server's machine and the actual client computer represented by a licence.
- Integrated the service into the mobility dashboard for production use.
Engineering highlights
Legacy compatibility
Preserved required behaviour while moving the integration onto a supported runtime.
Correct client representation
Resolved the boundary between the service host and the computer actually being licensed.
Reusable API
Wrapped five operations in a structured REST interface for modern applications.
Outcome
The service is integrated into the mobility dashboard and used in production, with internal licensing details kept private.