How kotagirilokesh-sonata/dotnetpoc works
ItemPortel is a small ASP.NET Core item API. An API client calls the item controller to list items or submit a new one; the controller reads or writes through Entity Framework, using the Item entity and SQL Server. Program starts the host and selects Startup, which configures controller routing, database services, CORS, and Swagger. The source excerpts show API and persistence behavior; no README or UI source documents additional product workflows.
Main entry points: Startup.cs HTTP configuration · TrainingDBContext.cs EF context · ItemController.cs Item endpoints · Program.cs Host entry
Components 8
Web hosting
- Host entry
ItemPortel/Program.cs - HTTP configuration
ItemPortel/Startup.cs - Swagger UI
ItemPortel/Startup.cs
Item API
- Item endpoints
ItemPortel/Controllers/ItemController.cs
Persistence
- Item entity
ItemPortel/Models/Item.cs - EF context
ItemPortel/Models/TrainingDBContext.cs
Other components
- API client
- SQL Server
Connections 8
- Host entry → HTTP configuration: starts with
ItemPortel/Program.cs - HTTP configuration → Item endpoints: routes controllers
ItemPortel/Startup.cs - HTTP configuration → EF context: configures database
ItemPortel/Startup.cs - HTTP configuration → Swagger UI: enables docs
ItemPortel/Startup.cs - API client → Item endpoints: requests items
ItemPortel/Controllers/ItemController.cs - Item endpoints → EF context: reads and writes
ItemPortel/Controllers/ItemController.cs - EF context → Item entity: maps entity
ItemPortel/Models/TrainingDBContext.cs - EF context → SQL Server: uses SQL Server
ItemPortel/Models/TrainingDBContext.cs