ASP.NET Core project structure — minimal APIs vs controllers, layer
95
93%
Does it follow best practices?
Impact
100%
2.50xAverage score across 5 eval scenarios
Passed
No known issues
Build the backend API for an e-commerce platform using ASP.NET Core with Entity Framework Core and SQLite. The platform handles customers, products, and orders. Each order belongs to a customer and contains multiple order items, each referencing a product.
The API needs endpoints for:
The system should handle error cases like products not found, invalid order data, and customers that don't exist. Connection details and any application settings should be configurable, not baked into the code. The app should also serve a simple static HTML page at the root.
A separate test project should accompany the main application.
Produce the project under a directory called ECommerceApi/ with a test project at ECommerceApi.Tests/. Each file should contain valid C# code (correct namespaces, using statements, class/method declarations). Full business logic implementation is not required but the code structure and class skeletons should be complete.
Include a project-structure.txt file at the root listing the directory tree.
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
skills
aspnet-project-structure
verifiers