Feb 8 2021 Arlington .NET / Nick Escalona

• place orders to store locations for customers
• add a new customer
• search customers by name
• display details of an order
• display all order history of a store location
• display all order history of a customer
• client-side validation [new]
• server-side validation [new]
• exception handling
• persistent data; no prices, customers, order history, etc. hardcoded in C#
• logging of exceptions, EF SQL commands, and other events [newly required]
• (optional: order history can be sorted by earliest, latest, cheapest, most expensive)
• (optional: get a suggested order for a customer based on his order history)
• (optional: display some statistics based on order history)
• (optional: asynchronous network & file I/O)

• use EF Core (either database-first approach with a SQL script or code-first approach with migrations) [newly changed]
• use an Azure SQL DB in third normal form
• don't use public fields
• define and use at least one interface

• class library
• contains all business logic
• contains domain classes (customer, order, store, product, etc.)
• documentation with <summary> XML comments on all public types and members (optional: <params> and <return>)
• (recommended: has no dependency on UI, data access, or any input/output considerations)

• has first name, last name, etc.
• (optional: has a default store location to order from)

• has a store location
• has a customer
• has an order time (when the order was placed)
• can contain multiple kinds of product in the same order
• rejects orders with unreasonably high product quantities
• (optional: some additional business rules, like special deals)

• has an inventory
• inventory decreases when orders are accepted
• rejects orders that cannot be fulfilled with remaining inventory
• (optional: for at least one product, more than one inventory item decrements when ordering that product)

• ASP.NET Core web API
• serve static HTML, CSS, JS, image, etc. files
  • communicate with the server and manage the page via JS
• receive and respond to AJAX requests
• use dependency injection with controllers, repositories, the context, and other services
• has only HTTP-related code

• class library
• separate project for data access code using EF Core
• contains data access logic but no business logic
• use repository pattern for separation of concerns

• at least 10 test methods
• focus on unit testing business logic
• data access tests (if present) should not impact the app's actual database [new]