Finish ASP.NET Pet Services Platform
Budget: $30 – $250 USD
The core of my pets-services platform is already running on C#, ASP.NET Core and SQL Server, but only part of the roadmap is complete. I need a developer who can dive into the existing repository, understand what’s been built so far and then work alongside me, sprint by sprint, until we launch. and after we launch stay with me to develop it more.
Where things stand
• Current status: partially developed. Key models, some controllers and basic pages are live, but several workflows still stop at stubs or placeholders.
• Guidelines: I have an architecture outline, UX wireframes and a list of required endpoints; however, I’m open to your recommendations on best practices, performance tuning, and UI polish.
What you’ll be picking up
– Clean up and extend the existing ASP.NET Core MVC / Razor Pages code.
– Wire remaining SQL Server tables through Entity Framework (or raw SQL if we decide it’s faster).
– Implement or refine modules such as user authentication, service listings and payment processing—exact priorities will come from our first planning call.
– Strengthen error handling, logging and unit testing so the platform is production-ready.
– Push to our private Git repo with clear commit messages; we’ll review via pull requests.
Deliverables
1. Incremental code pushes that compile and run locally.
2. A short change log for each milestone.
3. Deployment guidance for my Azure staging slot (currently hosting the partial build).
Acceptance criteria
• Each completed feature passes the test suite and manual smoke tests.
• No critical bugs in the staging environment for 48 hours after merge.
• Documentation is updated before we move to the next sprint.
I’m looking for someone comfortable pairing with a product owner, asking the right questions and keeping communication fluid on Slack or Teams. If that sounds like you, let’s talk timelines and start committing code.
Where things stand
• Current status: partially developed. Key models, some controllers and basic pages are live, but several workflows still stop at stubs or placeholders.
• Guidelines: I have an architecture outline, UX wireframes and a list of required endpoints; however, I’m open to your recommendations on best practices, performance tuning, and UI polish.
What you’ll be picking up
– Clean up and extend the existing ASP.NET Core MVC / Razor Pages code.
– Wire remaining SQL Server tables through Entity Framework (or raw SQL if we decide it’s faster).
– Implement or refine modules such as user authentication, service listings and payment processing—exact priorities will come from our first planning call.
– Strengthen error handling, logging and unit testing so the platform is production-ready.
– Push to our private Git repo with clear commit messages; we’ll review via pull requests.
Deliverables
1. Incremental code pushes that compile and run locally.
2. A short change log for each milestone.
3. Deployment guidance for my Azure staging slot (currently hosting the partial build).
Acceptance criteria
• Each completed feature passes the test suite and manual smoke tests.
• No critical bugs in the staging environment for 48 hours after merge.
• Documentation is updated before we move to the next sprint.
I’m looking for someone comfortable pairing with a product owner, asking the right questions and keeping communication fluid on Slack or Teams. If that sounds like you, let’s talk timelines and start committing code.
Related categories:
.NET
C# Programming
Azure
MVC
ASP.NET
Microsoft SQL Server
Git
.NET Core
API Development
Performance Tuning