How receperturkk/shadowstore-backend works
Project type and purpose
• This is a monolithic ASP.NET Core Web API backend (“ShadowStore-Backend”) that exposes product and user endpoints, uses ADO.NET for data access, and SQL Server (with stored procedures) as its database.
• Its primary purpose is to handle CRUD operations (via stored procedures) for a “ShadowStore” e-commerce or inventory system, serving requests on port 5001 to a separate frontend.
File structure
• Top-level files:
• ShadowStore.sln – Visual Studio solution
• database.sql – schema + stored-procedure definitions
• publish/ – contains the self-contained published app (exe, runtimes, config)
• ShadowStore/ directory holds the API source:
• Controllers/Products.cs, User.cs – HTTP API endpoints
• Product.cs – domain model (POCO)
• Program.cs – host and middleware setup (Kestrel, routing)
• appsettings.json & appsettings.Development.json – configuration (connection strings, ports)
• ShadowStore.csproj – project definition, dependencies
• No separate “DataAccess” folder, but data access occurs inline in controllers (ADO.NET calls to stored procedures).
Key README insights
• Database setup steps: create “shadowStore” database in local SQL Server, run database.sql
• The published exe must run on port 5001 to match the frontend’s expectations.
• Emphasis on ADO.NET + stored procedures for Add, Delete, Update operations.