Software, Web & AI Solutions

ABP.IO Expertise

ABP.IO Development,
Upgrades & Support

Specialist development for existing ABP.IO applications, including framework upgrades, application modernisation, integrations, ongoing maintenance and additional engineering capacity.

Discuss Your ABP.IO Project Staff Augmentation

Existing Applications

Already Working With an ABP.IO Application?

An ABP.IO application is rarely finished. Business requirements evolve, modules get added or reshaped, integrations expand, dependencies move forward and front-end requirements change — often while the original development team has moved on.

EKSTRUH can review an existing implementation and work out an appropriate development, upgrade, modernisation or maintenance approach for it, based on how that particular application has been put together rather than on a standard template.

Taking responsibility for an inherited application follows an initial technical review. That review is what tells us whether we can help and what the work would realistically involve.

Development for Existing ABP.IO Applications

Much of the ABP.IO work we are asked about is not recovery work — it is continued development on an application that is already doing its job and needs to do more.

Where an existing application is suitable, we can extend it with new business functionality: application services and domain logic, new API functionality, front-end development and UI improvements, database-related development, integrations, and extensions to modules that already exist. Technical refactoring is included where it is justified by the work in hand, not as an end in itself.

ABP.IO covers a wide surface area, including optional and commercial components. We scope against what an application actually uses rather than claiming familiarity with every available module.

ABP.IO Services

Four specialist areas, applied to applications already built on ABP.IO.

ABP.IO Framework Upgrades

For existing ABP.IO applications that need to move forward across framework, .NET, front-end or dependency versions.

An ABP.IO upgrade is not necessarily a package-version change. The framework, the .NET platform and the front end each move on their own schedule, and an application sits at the intersection of all three. Work normally starts with assessing the current implementation and reviewing module and dependency compatibility, then moves through breaking-change and custom-code assessment to testing and release planning.

How involved that becomes depends on the current version, the application architecture, the customisations and modules in place, the dependencies, the front end and the integrations around it.

Discuss an ABP.IO Upgrade

Typical upgrade work

  • Current implementation assessment
  • Framework version review
  • Dependency review
  • .NET compatibility
  • Front-end compatibility where applicable
  • Breaking-change assessment
  • Custom-code compatibility
  • Module compatibility
  • Database and migration considerations
  • Integration compatibility
  • Testing
  • Release planning

ABP.IO Migration & Modernization

For applications that need broader architectural, front-end or technical improvement rather than only a framework update.

Not every ABP.IO application needs this. Plenty are well structured and simply need upgrading and extending. Where modernisation is worthwhile, it is usually because specific problems have been identified — a module boundary that no longer reflects the business, ageing dependencies, a front end that has fallen behind, or integration points that have become awkward to change.

We favour incremental work over rewrites. Restructuring and component replacement happen where there is a clear reason, and technical debt is addressed where it has been identified rather than assumed.

Discuss Modernisation

Potential scope

  • Architecture assessment
  • Application restructuring where justified
  • Dependency modernisation
  • Front-end modernisation
  • Module review
  • Integration improvements
  • UI improvements
  • Technical debt reduction where clearly identified
  • Incremental migration
  • Selected component replacement

ABP.IO Support & Maintenance

Engineering attention for ABP.IO applications that are already in production and need to keep working while they keep changing.

In modular applications, maintenance tends to span several areas at once: a change in one module can touch shared functionality, an API contract or a front-end view. Support work therefore covers the backend, the modules, the integrations and the front end rather than treating them separately.

How much attention an application needs varies with its module count, integration surface and release cadence, so we agree the arrangement against the application in front of us.

Discuss Ongoing Support

What support can cover

  • Bug investigation
  • Framework updates
  • Dependency updates
  • Feature development
  • Module maintenance
  • API and integration maintenance
  • Front-end maintenance
  • Technical troubleshooting
  • Performance investigation
  • Codebase improvements
  • Release support

Dedicated ABP.IO Engineers

Add ABP.IO development capacity to an existing application or software team.

This suits teams whose roadmap is clear but whose capacity is not — a feature backlog that keeps slipping, an upgrade nobody has time to own, or integration work running alongside continued product development.

Engagement details are agreed per project.

Dedicated Engineers

Common engagement needs

  • Feature development
  • Application extension
  • Framework upgrades
  • Modernisation
  • Bug fixing
  • Integration development
  • Maintenance backlog
  • Additional engineering capacity

Working With Modular Business Applications

ABP.IO is commonly used where functionality is organised into modules or bounded areas rather than one undivided codebase. Depending on how the application has been designed, that structure can be strictly observed, partially applied, or looser than the original intent.

Practical work means paying attention to how functionality is separated, what depends on what, where shared functionality sits, how application services are exposed, where data boundaries fall and which points connect outwards to other systems.

Where those boundaries hold, applications stay easier to change as they grow. Where they have blurred over time, that is usually worth understanding before adding to the application rather than after.

A Structured Approach to ABP.IO Upgrades

Dependency mapping gets its own stage here for a reason: in modular applications it is usually the dependencies between modules and packages, not the framework version itself, that determine how much work an upgrade becomes.

  1. Review

    Identify current ABP.IO, .NET and front-end versions plus application customisations.

  2. Map dependencies

    Review modules, packages, integrations and compatibility considerations.

  3. Plan

    Define an appropriate upgrade sequence and identify areas requiring additional work.

  4. Upgrade

    Update the framework and application components and address required compatibility changes.

  5. Verify

    Test business functionality, integrations and affected application areas.

  6. Release & continue

    Deploy appropriately and address follow-up development or maintenance.

Working Across the ABP.IO Application Stack

The exact technology mix depends on the application's architecture and version. ABP.IO supports more than one front-end and database choice, so not every application uses the combination above.

Backend

  • .NET
  • ASP.NET Core

Framework

  • ABP.IO

Frontend

  • Angular
  • TypeScript
  • JavaScript
  • HTML5
  • CSS3

Data

  • SQL Server

Integration

  • REST APIs
  • Webhooks

ABP.IO & Angular Development

Where an ABP.IO implementation uses Angular, development and upgrade work usually involves both sides of the application at once.

That typically brings in Angular versions and TypeScript compatibility, front-end dependencies, the application UI, the API contracts between front end and backend, build and configuration changes, and authentication integration where it is relevant.

Our front-end work is covered on the Angular expertise page.

Connecting ABP.IO With Other Business Systems

An ABP.IO application usually sits within a wider software environment rather than on its own.

Where required, development work can involve connecting it to internal and external APIs, databases, authentication systems, other business platforms and workflow systems — including maintaining those connections as the systems either side of them change.

This overlaps with our business systems and integrations work.

Considering ASP.NET Zero and ABP.IO?

Some organisations with an existing ASP.NET Zero application evaluate ABP.IO as part of a wider modernisation strategy. It is a reasonable question to ask, and it deserves an assessment rather than an assumption.

That assessment looks at the current application and its business functionality, the custom code, the front end, the database, the integrations, the dependencies and what the organisation is actually trying to achieve by moving.

The outcome may be to continue with the existing ASP.NET Zero application, to upgrade it, to modernise it incrementally, to migrate selected functionality, or to undertake a broader migration where that is justified. Migration between the two is project work, not a conversion step, and a direct path is not always available.

Our ASP.NET Zero expertise page covers work on existing ASP.NET Zero applications.

When ABP.IO Expertise Can Help

Situations where framework-specific help tends to be worth bringing in.

  • An existing ABP.IO application needs new functionality
  • The framework or .NET version needs upgrading
  • Front-end dependencies also need attention
  • The original development team is no longer available
  • The application needs ongoing maintenance
  • Existing modules or integrations need extending
  • Additional ABP.IO development capacity is required
  • A broader modernisation project is being planned

Related Expertise

ASP.NET Zero

Upgrades, modernisation and support for existing ASP.NET Zero applications.

Angular

Front-end version upgrades, modernisation and continued development.

Have a Software Project in Mind?

Whether you're building something new, modernising an existing application or need specialist development support, let's discuss what you need.

Start a Project info@ekstruh.dev