Contact person: Legacy MVC to .NET Core API

Phone:Show

Email:Show

Location: Rawalpindi, Pakistan

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"I need to migrate several legacy .NET MVC controller classes into a clean, versioned RESTful API built on .NET Core. The goal is to keep every existing feature running exactly as it does today while modernising the stack and adopting current design standards and best practices.

Scope
The original controllers encapsulate business logic, data access and some inline validation. Your job is to refactor this code into a layered .NET Core Web API project that follows REST conventions, uses dependency injection, async/await throughout and separates concerns (controllers, services, repositories, DTOs). Authentication must be switched to stateless JWT tokens generated and validated inside the new API.

I will provide the full legacy project and highlight the controllers that need conversion. Any view-only code can be ignored; the focus is strictly on controller logic and its dependencies.

Deliverables
• Fully functional .NET Core Web API solution compiling under the latest LTS version
• Migrated endpoints mirroring the original routes or new, clearly documented REST routes
• JWT authentication integrated and sample token generation endpoint included
• Updated data validation using Data Annotations or FluentValidation where applicable
• README with setup instructions and any migration notes

Acceptance criteria
1. All legacy unit or integration tests (if present) pass against the new API, or equivalent tests are recreated.
2. Each migrated endpoint returns identical or contract-compatible payloads.
3. No controller contains direct data-access code; logic is abstracted behind interfaces.
4. Code respects C# naming conventions, nullable reference types are enabled and warnings are resolved.

Timeline and milestones are flexible; quality and maintainability are the priority. If parts of the original logic are unclear, I’ll be available to walk through them and supply missing documentation. it is just one controller so cose should be only 30-70$ it has 20-30 methods." (client-provided description)