Legacy MVC to .NET Core API -- 2

@designysoft

I understand your need for migrating your legacy .NET MVC controller classes to a clean, versioned RESTful API built on .NET Core. With over two decades of experience as a Senior Software Architect, I bring the precise skills you're seeking to this project. I have deep expertise in .NET, .NET Core and AS..P.. tourney with specific emphasis on developing REST APIs and Microservices Architecture. What sets me apart is my ability to integrate today's best practices, such as using dependency injection, async/await operations, and ensuring separation of concerns in your codebase. Being fully conversant with JWT authentication, I can easily reconfigure your code for stateless tokens that are generated and validated within the new API. Enabled with escriber référentielsandid data typesetat<optiontal reference types enabled and warnings are resolved->Moreover, I will ensure that each migrated endpoint mirrors either the previous routes or appropriately documents the new REST routes.

@softsolution2000

My Tasks include refactoring legacy .NET MVC controllers into a clean, RESTful API on .NET Core, following best practices. I will ensure async/await, dependency injection, and JWT authentication are implemented. Deliverables include a fully functional .NET Core Web API solution with updated data validation. I will prioritize quality and maintainability, ensuring all legacy tests pass. The budget can be adjusted after discussing the full scope. Please review my profile for my extensive experience. Looking forward to discussing the details and starting the project.

@ZohaibRoy

⭐⭐⭐⭐⭐ Migrate Legacy .NET MVC Controllers to a Modern RESTful API ❇️ Hi My Friend, I hope you're doing well. I've reviewed your project needs and noticed you're looking for a migration of .NET MVC controllers to a RESTful API. You have no need to look any further; Zohaib is here to help you! My team has successfully completed over 50 similar projects for API development and migration. I will refactor your existing code into a clean .NET Core Web API, ensuring all features work as they do now while modernizing the stack. ➡️ Why Me? I can easily handle your migration project as I have 5 years of experience in .NET development, focusing on building RESTful APIs, dependency injection, and async programming. My expertise includes controller logic, service and repository patterns, and JWT authentication. Additionally, I have a strong grip on other relevant technologies that will ensure a smooth transition for your project. ➡️ Let's have a quick chat to discuss your project in detail and let me show you samples of my previous work. Looking forward to discussing this with you in our chat. ➡️ Skills & Experience: ✅ .NET Core Development ✅ RESTful API Design ✅ MVC Architecture ✅ Dependency Injection ✅ JWT Authentication ✅ Async Programming ✅ Data Validation ✅ Business Logic Implementation ✅ Unit Testing ✅ FluentValidation ✅ C# Naming Conventions ✅ Code Optimization Waiting for your response! Best Regards, Zohaib

@Ranuka

My Tasks Hello, I’m Ranuka, a Senior .NET Developer with 12+ years of experience in ASP.NET MVC and .NET Core API development. I will set up a clean .NET Core Web API project and convert one controller method from your legacy MVC code into a properly structured, RESTful endpoint using best practices. What I Will Do: Setup project with layered architecture (Controllers, Services, Repositories, DTOs) Implement dependency injection and async/await pattern Convert one selected controller method with full logic refactoring Add JWT-based authentication setup Ensure clean, maintainable, and extensible structure Ranuka

@GediminasB

I am an old certificated .NET/C# programmer working with .NET for 25 years. I know all ASP.NET MVC versions, including ASP.NET Core and WEB API, Blazor. I shall build ASP.NET Core WEB API with latest version of Visual Studio Insiders 2026 using the latest version of .NET. I live in Lithuania (+2GMT). Human languages: Lithuanian (native), English, Russian (at mother tongue level).

@GameOfWords

'My tasks on this project would be to migrate your legacy .NET MVC controller classes into a clean, versioned RESTful API on .NET Core. With extensive knowledge and experience in .NET, .NET Core, and API development along with working proficiency in C# Programming, I can confidently say that I am well-suited for these tasks. My process involves diligently refactoring the code into layered .NET Core Web API projects, ensuring all your existing features continue to function seamlessly while also adhering to the contemporary best practices and design standards. To achieve this, I prioritize separating concerns using controllers, services, repositories, DTOs approach and implementing dependency injection. One aspect of migrating controllers is understanding business logic and encapsulating it properly. This is an area where I excel; my passion for detail ensures no direct data-access codes are present in the controllers and that logic is abstracted behind interfaces as needed. By choosing me, you're not only getting a developer efficient in legacy migrations but someone dedicated to following naming conventions, enabling nullable reference types and resolving potential warnings - all yielding clean, maintainable code.''

@sf264

My Tasks Hello, I can migrate several legacy .NET MVC controller classes into a clean, versioned RESTful API built on .NET Core. I would love to discuss more details via chat. Looking forward to working with you, Fahad.

@mkh559a5a1fd66e9

My Tasks involve converting a single controller, but this doesn't mean I'll be cutting corners with the quality. With over a decade-long tenure in .NET and an impressive list of tools at my disposal, transforming your legacy MVC into a modern .NET Core API will be nothing short of seamless for me. My skillset extends to vital areas including C#, ASP.NET, MVC, .NET Core and more - all the core components for this project adaptation. Whether it's handling encoding issues with Data Annotations or implementing your desired JWT stateless tokens authentication on .NET Core Web API, I have the know-how to do it all in line with contemporary best practices. The beauty of my work is not only about efficient code; it's also about reliable solutions that stand the test of time. By 'abstracting logic behind interfaces', I plan to ensure no controllers hold direct data-access codes, making your application easier to scale and maintain. Additionally, I will equip your new API with detailed documentation and sample token generation endpoint for your convenience. I understand that cost-effectiveness matters to you, which is why I can assure you superior work at a competitive rate - always with an eye on optimizing efficiency, ensuring quality and maintainability. Let me do what I do best by entrusting this project to me so you can rest assured that you’ll have a modernized API built on netcore that functions as smoothly as ever!

@anandan1995

Hello, I have read your job description and I am interested in your job post. I am ready to start now. Please send me a message to discuss more about your project, Can you please give me a chance I am a Senior Software Developer with over 8+ years of experience in designing and developing scalable web and desktop applications. I specialize in Microsoft technologies and delivering high-quality, secure, and performance-driven applications. My Expertise: Backend Development:ASP.NET, ASP.NET Core, MVC, Web API, WebForms, WCF Services Programming Languages:C#, Frontend Development:JavaScript, jQuery, AJAX, HTML, CSS Database Technologies:SQL Server, MySQL Reporting Tools:Crystal Reports, RDLC, SSIS, SSRS

@albertc1996

My Tasks Having spent 9+ years working deep in the .NET ecosystem — including a recent role where I refactored legacy modules following SOLID principles and clean architecture — this project is squarely in my wheelhouse. I've done exactly this kind of migration before, and I know where the traps are. Here's what I'll deliver for the single controller conversion: — A clean .NET Core Web API project scaffold: layered structure (Controllers → Services → Repositories → DTOs), dependency injection wired up, async/await throughout, and nullable reference types enabled with zero warnings. — The target controller fully migrated: all methods converted to proper REST endpoints, business logic lifted out of the controller and placed behind interfaces, zero direct data-access code in the controller layer. — JWT authentication: stateless token generation and validation integrated into the project, including a sample /auth/token endpoint so you can test it immediately. — Data validation: existing inline validation replaced with Data Annotations or FluentValidation, whichever fits the existing logic better. — A README covering setup steps, how to run the project, and any migration notes worth flagging for the remaining controllers you'll handle yourself. A couple of things I want to be upfront about: I won't touch view-only code — strictly controller logic and its dependencies, exactly as scoped. If I run into anything ambiguous in the legacy code, I'll come to you directly rather than make assumptions that could break behaviour. On testing: if the legacy project has existing unit or integration tests, I'll make sure they pass against the new API. If there are none, I'll write equivalent tests for the migrated controller so you have a baseline to build on. Timeline is flexible on my end too — I'd rather take an extra day and hand you something maintainable than rush and leave you cleaning up later. Budget: $130 — fixed price, no surprises. I'm available to jump on a quick call to walk through the legacy code together before I start, which usually saves time for both sides. Let me know if you'd like to proceed.

@antonk52

✔✔✔Hold on!! Looking for a Developer Who Gets Results? Hire Me, Relax, and Watch Your Project Turn Into Success✔✔✔ Your requirement is clear—but this job legally requires a Georgia-licensed PE, and I want to be upfront: I’m not a licensed GA PE, so I cannot stamp plans myself. However, I can still help you get this approved fast by: • Revising your PDFs/DWGs (LOD, buffers, floodplain overlays, slopes, driveways) • Preparing GSWCC-compliant E&S updates • Creating a clean comment-response memo • Coordinating with or handing off to a GA PE for final stamp Cost (revision only): $300–$600 (prep work) PE stamp (via partner): typically $400–$800 Timeline: 3–5 days revisions + 1–2 days stamping This approach is faster and avoids costly redesign delays. If you already have a PE, I’ll prepare everything ready for immediate signing.

@juliotrasferetti

Greetings! I’m Julio Trasferetti, a Computer Engineer with 12+ years of experience specializing in .NET modernization. I can refactor your legacy MVC logic into a clean, layered .NET Core Web API with JWT authentication and async/await throughout. I will set up the project architecture (Services, Repositories, DTOs) and migrate the first controller to serve as the perfect blueprint for the rest of your migration, ensuring 1:1 functional parity. My workflow is transparent, and I have samples of similar API refactoring to show you. Bests

@gptanjali98

I will set up a modern .NET Core Web API project (latest LTS) and migrate one of your legacy MVC controller methods into a clean, layered architecture while preserving its exact behavior and response structure. ? What I’ll Deliver Full project setup with: Proper folder structure (Controllers, Services, Repositories, DTOs) Dependency Injection configured Async/await pattern applied Nullable reference types enabled One fully converted controller + method: Matches existing functionality and output Refactored into service + repository layers No direct data access inside the controller JWT Authentication setup: Token generation endpoint Middleware for validation Ready for scaling across other endpoints Validation upgrade: Using Data Annotations or FluentValidation (based on your preference) README documentation: How to run the project How to test the endpoint Clear pattern to replicate remaining controllers ? Approach I will focus on creating a reusable architecture template, so you can easily migrate the remaining controllers yourself with consistency and speed. ⏱️ Timeline & Cost Since this is limited to: Project setup One controller + one method conversion I can complete this within 1–2 days at a reasonable budget. This will give you a solid, production-ready foundation without overpaying for full migration. Best regards, Prashant

@ddtechz

My Tasks I’ll set up a clean .NET Core Web API project using the latest LTS version and structure it with proper layers (controllers, services, repositories, DTOs). I’ll migrate one selected controller method from your legacy MVC project, ensuring the logic remains exactly the same while refactoring it to follow REST standards, async/await, and dependency injection. I’ll also configure JWT-based authentication with a sample token endpoint, and apply proper validation using Data Annotations or FluentValidation where needed. The goal is to give you a solid, production-ready foundation so you can continue migrating the remaining methods smoothly. I have strong experience modernizing legacy .NET systems (including separating business logic, handling migrations from MVC/WCF to REST, and keeping behavior unchanged), so I’ll make sure the converted method is clean, consistent, and easy to replicate. I’ll deliver a working solution, clean architecture setup, one fully migrated controller method, and a short README to guide further migration. Thanks, Deo

@mubeenm5026

My Tasks with your MVC to .NET Core API project will include a careful and comprehensive conversion of your legacy .NET MVC controller classes into a RESTful API on the .NET Core framework. With my deep experience in .NET and C# programming, you can trust that I’ll handle this migration with precision and efficiency. My knack for following best practices and adhering to design standards means your legacy features will continue to function perfectly after the transition. I specialize in separating concerns in complex projects like yours, which assures that your new API will respect current industry conventions and separate responsibilities for clean code organization. I will create clearly documented REST routes mirroring your original routes or designing new ones where appropriate. Moreover, I'll ensure stateless JWT authentication is seamlessly integrated, including a sample token generation endpoint, for robust security. What sets my team apart at Web Crest is our commitment to not just meeting specifications but exceeding expectations. Your satisfaction lies at the heart of each task we undertake, so every piece of functionality will be thoroughly tested before project delivery. From updated data validation using Data Annotations or FluentValidation to a comprehensive README with setup instructions and even migration notes - I’ll handle it all so you don't have to worry about anything except for project setup and one controller creation

@ztconnect

Dear Hiring Manager, I’m excited to apply for the "Legacy MVC to .NET Core API -- 2" you posted. With over 8 years of software development experience, my skills and experience are well-suited to the needs of this project. Available for immediate start and would welcome the opportunity to discuss this project in more detail. Please feel free to contact me. Thank you, Zahid T.

@csijindioy

My Tasks include, migrate your legacy MVC controller into a clean .NET Core Web API following strict REST conventions. I’ll set up a layered architecture (controllers, services, repositories, DTOs), implement async/await, and integrate stateless JWT authentication. I will convert one selected method to demonstrate the full migration pattern, ensuring identical behavior and payloads. All logic will be refactored behind interfaces with proper validation and clean separation of concerns.

@prshahbaz

Hi, My Tasks are to set up a clean .NET Core Web API structure and migrate one controller method with proper layering, so you can replicate the rest easily. I’ll convert your legacy MVC logic into a modern, maintainable architecture with: ✔ Controller → Service → Repository separation ✔ Async/await + dependency injection ✔ JWT authentication (token generation + validation) ✔ Clean DTOs + validation (Data Annotations/FluentValidation) I’ve done similar refactoring in ERP and API systems, where preserving behavior while improving structure was critical. I’ll ensure the migrated method returns identical output and follows REST standards. Deliverables: • Ready-to-use .NET Core API project (latest LTS) • One fully migrated controller method as reference • JWT setup + sample endpoint • Clear README for extending remaining methods Budget: Within your range ($30–70) Availability: Ready to start immediately Best, Shahbaz

@SaudSaeed67

Hi, I have thoroughly reviewed the requirements, and I am interested in this opportunity to help migrate your legacy .NET MVC controller logic into a modern, clean .NET Core Web API architecture while ensuring all existing functionality remains intact. For this task, I will set up a .NET Core Web API solution using the latest LTS version, structured with proper separation of concerns including Controllers, Services, Repositories, and DTOs, and configured with dependency injection and async/await patterns. I will also integrate stateless JWT authentication with a sample token generation endpoint. As requested, I will convert one controller method from the legacy MVC project as a reference implementation, ensuring the logic, routes, and response contracts remain consistent with the existing system. This will provide a clear template so you can easily migrate the remaining methods yourself. I will also include modern validation (Data Annotations or FluentValidation) and provide a README with setup instructions and migration notes. Since the scope mainly involves project setup and one controller implementation. I focus on writing clean, maintainable, and well-structured code so the rest of the migration process becomes straightforward. I would be happy to review the legacy controllers you provide and begin the setup immediately. Looking forward to working with you. Best regards, Saud S.