New features and modules
Develop ASP.NET Core, MVC and WebForms applications, APIs, business workflows, dashboards and integrations.
I develop existing applications, build new features and help regain control of ASP.NET Core, MVC, WebForms, APIs, Windows services and SQL databases. The scope can be one module, regular product development or a staged modernisation of the system.
Develop ASP.NET Core, MVC and WebForms applications, APIs, business workflows, dashboards and integrations.
Map architecture, dependencies, risks and deployment. Deliver priorities and a first-stage plan with quotation assumptions and acceptance criteria.
Assess library compatibility and .NET Framework dependencies. Separate selected processes, define module communication and replace older components gradually.
Clarify module responsibilities, refactor and update .NET and libraries within an agreed scope, checking existing functionality.
Diagnose queries and locks, improve models and indexes and plan migrations with consistency checks. Measure representative operations before and after.
Develop APIs, Windows services, imports and scheduled jobs with errors, retries and duplicate handling so operations can be traced and resumed.
Protect critical paths, organise environments and automate publishing. Include data migration, rollback conditions and deployment instructions.
Add logs, alerts and measurements. Document important decisions, startup and diagnostics and explain changes to the maintenance team.
Identify critical processes, reproduce startup and add tests and diagnostics. The current application and database establish a baseline.
Move on when the team can reproduce and verify the main operations.
Move an agreed process into a new .NET module while the old application handles the rest. Define communication, permissions and read/write ownership.
Move on when the new module meets acceptance criteria and existing workflows still pass their checks.
Choose the next area after verifying the first. Retire replaced components only after confirming functionality and data consistency.
Measurements and business needs should justify the next stage. Agree downtime, cutover and rollback before deployment.
Start with a problem description, technology details and agreed access to code or an environment. Missing documentation can be reconstructed during diagnosis. Deliverables include the system and dependency map, risks and priorities, and a first-stage plan with scope, assumptions and acceptance criteria.
Describe the problem, system and desired result.
Data, risks, feasibility and measurement.
A small scope that validates the solution.
Integration, tests, monitoring and documentation.
Measure results and continue improving.
Not always. Assess dependencies, risks and change costs first. Stabilisation, selective upgrades and module separation are often safer starting points.
A dependency and risk map, technical priorities, modernisation options, a recommended first stage and information needed to estimate further work.
Often, in stages. Each change needs suitable tests, deployment arrangements, monitoring and rollback; the actual plan depends on architecture and data.
Yes, when responsibilities can be separated. Moving to ASP.NET Core requires assessing UI, business logic, session state, permissions and dependencies; it is more than changing a project version.
Yes: a screen, module, integration, performance improvement or deployment work. We first establish dependencies and acceptance criteria to contain the scope.
Briefly describe the situation. I will recommend a sensible first step — without a sales pitch or obligation.