trainer-demo-deploy: Instructions file for GitHub Copilot

.NET 10 Web Application Instructions

Framework Requirements

• Target framework: net10.0 — always use the latest .NET 10
• Project type: ASP.NET Core Razor Pages (dotnet new webapp)
• Data strategy: Use the Azure data service (Storage Table, SQL, Cosmos DB, etc.) when the architecture includes one. Fall back to local JSON seed files only when no data endpoint is specified.

Project Structure

{ProjectName}.Web/
├── {ProjectName}.Web.csproj
├── Program.cs
├── appsettings.json
├── Models/           → Domain entity classes
├── Services/         → SampleDataService (in-memory JSON loader)
├── SeedData/         → JSON files with sample records
├── Pages/            → Razor Pages (Index + per-entity CRUD)
└── wwwroot/          → Static assets (CSS, JS)

Coding Standards

General

• Use file-scoped namespaces
• Use primary constructors where appropriate
• Prefer string.Empty over ""
• Initialize collection properties with new() or []
• Use required or = string.Empty for non-nullable string properties

Models

• Every model has an int Id property
• Use C# records for immutable data if appropriate
• Keep models flat — no deep object graphs
• Include 2-4 entities per industry domain

Services

• When an Azure data service is present: register the appropriate data service (e.g., TableStorageDataService) as singleton
• When no data endpoint: register SampleDataService as singleton
• Use System.Text.Json for deserialization (not Newtonsoft)
• Use Azure.Identity (DefaultAzureCredential) for authenticating to Azure services
• Load seed data lazily on first access
• Handle missing files gracefully (return empty list)

Razor Pages

• One page model per .cshtml.cs file
• Use constructor injection for SampleDataService
• Keep page models thin — delegate to service
• Use tag helpers for forms and links

Seed Data

• JSON files with 10-20 realistic but fictional records
• Use PascalCase property names in JSON (match C# models)
• Include varied data (different statuses, dates, amounts)
• No real personal information — use fictional names and addresses