.NET Core 2.2 to .NET 8 Migration
Budget: $500 – $1,000 USD
We are looking for an experienced .NET developer to migrate our existing monolithic RESTful API from .NET Core 2.2 to .NET 8. The API serves both mobile and web applications and is built with the following stack:
✅ .NET Core (to be migrated to .NET 8)
✅ PostgreSQL (Database)
✅ JSON-based API responses
✅ Entity Framework Core
✅ Authentication & Authorization (JWT, OAuth)
✅ Dependency Injection & Middleware
✅ Logging & Monitoring (log4net)
Project Scope & Requirements:
- Migrate from .NET Core 2.2 to .NET 8 while maintaining existing functionality.
- Ensure all 58 controllers function correctly after migration.
- 10 controllers are more complex (custom business logic), others are standard CRUD operations.
- Optimize and modernize the code where it makes sense, but all changes should be discussed in advance.
- Refactor deprecated methods and update dependencies as needed.
- Testing & Validation We have all necessary API request/response samples in Insomnia for easy testing.
- Results from the migrated API must match the current API.
Documentation:
- Well-commented and structured code.
- Clear documentation on changes made during migration.
- Performance & Security Considerations - Ensure no degradation in API performance.
- Apply best practices for security (e.g., improved authentication, HTTPS, rate limiting).
Who We’re Looking For:
- Experience in .NET Core & .NET 8 (hands-on migration experience preferred).
- Strong PostgreSQL & Entity Framework Core skills.
- Knowledge of RESTful API best practices and JSON handling.
- Familiarity with API authentication mechanisms (JWT, OAuth).
- Good understanding of asynchronous programming (async/await).
- Experience with testing tools (e.g., xUnit, NUnit, Postman/Insomnia).
- Ability to write clean, maintainable, and well-documented code.
- Strong communication skills (must be open to discussions about optimizations).
Timeline & Quality Expectations:
- No rush – quality is more important than speed.
- The project is complete when:
Code is fully migrated and well written.
- Tests pass (validated via Insomnia).
- Documentation is provided.
Any optimizations are agreed upon in advance.
- Using ChatGPT for coding is allowed, but only when reasonable (no blind AI-generated code).
✅ .NET Core (to be migrated to .NET 8)
✅ PostgreSQL (Database)
✅ JSON-based API responses
✅ Entity Framework Core
✅ Authentication & Authorization (JWT, OAuth)
✅ Dependency Injection & Middleware
✅ Logging & Monitoring (log4net)
Project Scope & Requirements:
- Migrate from .NET Core 2.2 to .NET 8 while maintaining existing functionality.
- Ensure all 58 controllers function correctly after migration.
- 10 controllers are more complex (custom business logic), others are standard CRUD operations.
- Optimize and modernize the code where it makes sense, but all changes should be discussed in advance.
- Refactor deprecated methods and update dependencies as needed.
- Testing & Validation We have all necessary API request/response samples in Insomnia for easy testing.
- Results from the migrated API must match the current API.
Documentation:
- Well-commented and structured code.
- Clear documentation on changes made during migration.
- Performance & Security Considerations - Ensure no degradation in API performance.
- Apply best practices for security (e.g., improved authentication, HTTPS, rate limiting).
Who We’re Looking For:
- Experience in .NET Core & .NET 8 (hands-on migration experience preferred).
- Strong PostgreSQL & Entity Framework Core skills.
- Knowledge of RESTful API best practices and JSON handling.
- Familiarity with API authentication mechanisms (JWT, OAuth).
- Good understanding of asynchronous programming (async/await).
- Experience with testing tools (e.g., xUnit, NUnit, Postman/Insomnia).
- Ability to write clean, maintainable, and well-documented code.
- Strong communication skills (must be open to discussions about optimizations).
Timeline & Quality Expectations:
- No rush – quality is more important than speed.
- The project is complete when:
Code is fully migrated and well written.
- Tests pass (validated via Insomnia).
- Documentation is provided.
Any optimizations are agreed upon in advance.
- Using ChatGPT for coding is allowed, but only when reasonable (no blind AI-generated code).