Upgrade to .NET 10.0, Aspire 13.x, and modernize infra

Upgraded all projects to .NET 10.0 and updated NuGet dependencies. Migrated Aspire AppHost to SDK 13.x with new SQL Server resource wiring and global.json pinning. Refactored Store ProductService for simpler image URL handling and added image caching. Introduced /api/images/{id} endpoint in Store for product image serving. Restored Cart/Checkout link in navigation and enabled Blazor interactive rendering for Checkout. Updated tests, benchmarks, and documentation. Added AGENTS.md, copilot_instructions.md, and improved scenario/task tracking.

Author: ralphke

.aspire/settings.json

@@ -0,0 +1,3 @@
+{
+  "appHostPath": "../src/TinyShop.AppHost/TinyShop.AppHost.csproj"
+}

.github/prompts/copilot_instructions.md

@@ -0,0 +1,51 @@
+
+# Workflow Orchestration
+
+## 1. Plan Node Default
+- Enter plan mode for ANY non-trivial task (3+ steps or architectural decisions)
+- If something goes sideways, STOP and re-plan immediately - don't keep pushing
+- Use plan mode for verification steps, not just building
+- Write detailed specs upfront to reduce ambiguity
+
+## 2. Subagent Strategy
+- Use subagents liberally to keep main context window clean
+- Offload research, exploration, and parallel analysis to subagents
+- For complex problems, throw more compute via subagents
+- One task per subagent for focused execution
+
+## 3. Self-Improvement Loop
+- After ANY correction from the user: update `workflows/lessons.md` with the pattern
+- Write rules for yourself that prevent the same mistake
+- Ruthlessly iterate on these lessons until mistake rate drops
+- Review lessons at session start for relevant project
+
+## 4. Verification Before Done
+- Never mark a task complete without proving it works
+- Diff behavior between main and your changes when relevant
+- Ask yourself: "Would a staff engineer approve this?"
+- Run tests, check logs, demonstrate correctness
+
+## 5. Demand Elegance (Balanced)
+- For non-trivial changes: pause and ask "Is there a more elegant way?"
+- If a fix feels hacky: acknowledge it and implement the cleaner solution
+- Skip fixes for simple, obvious fixes - don't over-engineer and focus on correctness first
+- Challenge your own work before presenting it
+
+## 6. Autonomous Bug Fixing
+- When given a bug report: just fix it. Don't ask for hand-holding
+- Point to logs, errors, failing tests - then resolve them
+- Zero context switching required from the user
+- Go fix failing CI tests without being told how
+
+## 7. Task Management
+1. **Plan First**: Write plan to `workflows/todo.md` with checkable items
+2. **Verify Plans**: Check plan before starting implementation
+3. **Track Progress**: Mark items complete as you go
+4. **Explain Changes**: High-level summary at each step
+5. **Document Lessons**: Add review section to `workflows/todo.md`
+6. **Capture Lessons**: Update `workflows/lessons.md` after corrections
+
+## Core Principles
+- **Simplicity First**: Make every change as simple as possible. Impact minimal code.
+- **No Laziness**: Find root causes, not temporary fixes. Senior developer standards.
+- **Minimal Impact**: Changes should only touch what's necessary. Avoid introducing bugs.

.github/upgrades/scenarios/new-dotnet-version_9488f4/scenario.json

@@ -3,7 +3,7 @@
   "operationId": "9488f4f1-bf3e-4e63-90e5-497fed7a2577",
   "description": "Upgrade solution or project to new version of .NET",
   "startTime": "2026-02-22T20:42:33.6358209Z",
-  "lastUpdateTime": "2026-02-22T21:14:29.2279666Z",
+  "lastUpdateTime": "2026-03-07T11:38:22.5815998Z",
   "stage": "Execution",
   "properties": {},
   "folderPath": ""

.github/upgrades/scenarios/new-dotnet-version_9488f4/tasks.md

@@ -4,33 +4,37 @@
 
 This document tracks the execution of the TinyShop solution upgrade from .NET 9.0 to .NET 10.0. All projects will be upgraded simultaneously in a single atomic operation, followed by verification.
 
-**Progress**: 0/2 tasks complete (0%) ![0%](https://progress-bar.xyz/0)
+**Progress**: 1/2 tasks complete (50%) ![0%](https://progress-bar.xyz/50)
 
 ---
 
 ## Tasks
 
-### [▶] TASK-001: Verify prerequisites
+### [✓] TASK-001: Verify prerequisites *(Completed: 2026-02-22 21:15)*
 **References**: Plan §Migration Strategy - Execution Steps
 
-- [▶] (1) Verify .NET 10.0 SDK installed per Plan §Executive Summary
-- [ ] (2) .NET 10.0 SDK is available (**Verify**)
-- [ ] (3) Check global.json compatibility (if present in repository)
-- [ ] (4) global.json compatible with .NET 10.0 or updated (**Verify**)
+- [✓] (1) Verify .NET 10.0 SDK installed per Plan §Executive Summary
+- [✓] (2) .NET 10.0 SDK is available (**Verify**)
+- [✓] (3) Check global.json compatibility (if present in repository)
+- [✓] (4) global.json compatible with .NET 10.0 or updated (**Verify**)
 
 ---
 
-### [ ] TASK-002: Atomic framework and package upgrade for all projects
+### [▶] TASK-002: Atomic framework and package upgrade for all projects
 **References**: Plan §Migration Strategy - Execution Steps, Plan §Detailed Dependency Analysis - NuGet Package Dependencies, Plan §Risk Management - Critical Issues
 
-- [ ] (1) Update TargetFramework to net10.0 in all 5 projects: DataEntities, TinyShop.ServiceDefaults, Products, Store, BenchmarkSuite1 per Plan §Migration Strategy - Upgrade Sequence
-- [ ] (2) All project TargetFramework properties updated to net10.0 (**Verify**)
-- [ ] (3) Update package references per Plan §Detailed Dependency Analysis - NuGet Package Dependencies (10 packages: Microsoft.EntityFrameworkCore 9.0.6→10.0.3, Microsoft.EntityFrameworkCore.Design 9.0.6→10.0.3, Microsoft.Extensions.Http.Resilience 9.6.0→10.3.0, Microsoft.Extensions.ServiceDiscovery 9.3.1→10.3.0, Microsoft.VisualStudio.Web.CodeGeneration.Design 9.0.0→10.0.2, OpenTelemetry.Instrumentation.AspNetCore 1.12.0→1.15.0, OpenTelemetry.Instrumentation.Http 1.12.0→1.15.0, System.Formats.Asn1 9.0.6→10.0.3, System.Text.Json 9.0.6→10.0.3)
-- [ ] (4) All package references updated (**Verify**)
-- [ ] (5) Restore all dependencies
-- [ ] (6) All dependencies restored successfully (**Verify**)
-- [ ] (7) Build solution and fix all compilation errors per Plan §Risk Management - Critical Issues (focus on Store project: fix TimeSpan.FromMinutes(5) to TimeSpan.FromMinutes(5.0) at Store\Services\ProductService.cs line 31)
-- [ ] (8) Solution builds with 0 errors (**Verify**)
-- [ ] (9) Commit changes with message: "TASK-002: Complete .NET 10.0 atomic upgrade for all projects"
+- [✓] (1) Update TargetFramework to net10.0 in all 5 projects: DataEntities, TinyShop.ServiceDefaults, Products, Store, BenchmarkSuite1 per Plan §Migration Strategy - Upgrade Sequence
+- [✓] (2) All project TargetFramework properties updated to net10.0 (**Verify**)
+- [✓] (3) Update package references per Plan §Detailed Dependency Analysis - NuGet Package Dependencies (10 packages: Microsoft.EntityFrameworkCore 9.0.6→10.0.3, Microsoft.EntityFrameworkCore.Design 9.0.6→10.0.3, Microsoft.Extensions.Http.Resilience 9.6.0→10.3.0, Microsoft.Extensions.ServiceDiscovery 9.3.1→10.3.0, Microsoft.VisualStudio.Web.CodeGeneration.Design 9.0.0→10.0.2, OpenTelemetry.Instrumentation.AspNetCore 1.12.0→1.15.0, OpenTelemetry.Instrumentation.Http 1.12.0→1.15.0, System.Formats.Asn1 9.0.6→10.0.3, System.Text.Json 9.0.6→10.0.3)
+- [✓] (4) All package references updated (**Verify**)
+- [✓] (5) Restore all dependencies
+- [✓] (6) All dependencies restored successfully (**Verify**)
+- [✓] (7) Build solution and fix all compilation errors per Plan §Risk Management - Critical Issues (focus on Store project: fix TimeSpan.FromMinutes(5) to TimeSpan.FromMinutes(5.0) at Store\Services\ProductService.cs line 31)
+- [✓] (8) Solution builds with 0 errors (**Verify**)
+- [▶] (9) Commit changes with message: "TASK-002: Complete .NET 10.0 atomic upgrade for all projects"
 
 ---
+
+
+
+

AGENTS.md

@@ -0,0 +1,61 @@
+# Copilot instructions
+
+This repository is set up to use Aspire. Aspire is an orchestrator for the entire application and will take care of configuring dependencies, building, and running the application. The resources that make up the application are defined in `apphost.cs` including application code and external dependencies.
+
+## General recommendations for working with Aspire
+1. Before making any changes always run the apphost using `aspire run` and inspect the state of resources to make sure you are building from a known state.
+1. Changes to the _apphost.cs_ file will require a restart of the application to take effect.
+2. Make changes incrementally and run the aspire application using the `aspire run` command to validate changes.
+3. Use the Aspire MCP tools to check the status of resources and debug issues.
+
+## Running the application
+To run the application run the following command:
+
+```
+aspire run
+```
+
+If there is already an instance of the application running it will prompt to stop the existing instance. You only need to restart the application if code in `apphost.cs` is changed, but if you experience problems it can be useful to reset everything to the starting state.
+
+## Checking resources
+To check the status of resources defined in the app model use the _list resources_ tool. This will show you the current state of each resource and if there are any issues. If a resource is not running as expected you can use the _execute resource command_ tool to restart it or perform other actions.
+
+## Listing integrations
+IMPORTANT! When a user asks you to add a resource to the app model you should first use the _list integrations_ tool to get a list of the current versions of all the available integrations. You should try to use the version of the integration which aligns with the version of the Aspire.AppHost.Sdk. Some integration versions may have a preview suffix. Once you have identified the correct integration you should always use the _get integration docs_ tool to fetch the latest documentation for the integration and follow the links to get additional guidance.
+
+## Debugging issues
+IMPORTANT! Aspire is designed to capture rich logs and telemetry for all resources defined in the app model. Use the following diagnostic tools when debugging issues with the application before making changes to make sure you are focusing on the right things.
+
+1. _list structured logs_; use this tool to get details about structured logs.
+2. _list console logs_; use this tool to get details about console logs.
+3. _list traces_; use this tool to get details about traces.
+4. _list trace structured logs_; use this tool to get logs related to a trace
+
+## Other Aspire MCP tools
+
+1. _select apphost_; use this tool if working with multiple app hosts within a workspace.
+2. _list apphosts_; use this tool to get details about active app hosts.
+
+## Playwright MCP server
+
+The playwright MCP server has also been configured in this repository and you should use it to perform functional investigations of the resources defined in the app model as you work on the codebase. To get endpoints that can be used for navigation using the playwright MCP server use the list resources tool.
+
+## Updating the app host
+The user may request that you update the Aspire apphost. You can do this using the `aspire update` command. This will update the apphost to the latest version and some of the Aspire specific packages in referenced projects, however you may need to manually update other packages in the solution to ensure compatibility. You can consider using the `dotnet-outdated` with the users consent. To install the `dotnet-outdated` tool use the following command:
+
+```
+dotnet tool install --global dotnet-outdated-tool
+```
+
+## Persistent containers
+IMPORTANT! Consider avoiding persistent containers early during development to avoid creating state management issues when restarting the app.
+
+## Aspire workload
+IMPORTANT! The aspire workload is obsolete. You should never attempt to install or use the Aspire workload.
+
+## Official documentation
+IMPORTANT! Always prefer official documentation when available. The following sites contain the official documentation for Aspire and related components
+
+1. https://aspire.dev
+2. https://learn.microsoft.com/dotnet/aspire
+3. https://nuget.org (for specific integration package details)

src/BenchmarkSuite1/BenchmarkSuite1.csproj

@@ -6,9 +6,9 @@
   </PropertyGroup>
 
   <ItemGroup>
-    <PackageReference Include="BenchmarkDotNet" Version="0.15.2" />
-    <PackageReference Include="Microsoft.EntityFrameworkCore.InMemory" Version="10.0.3" />
-    <PackageReference Include="Microsoft.VisualStudio.DiagnosticsHub.BenchmarkDotNetDiagnosers" Version="18.3.36726.2" />
+    <PackageReference Include="BenchmarkDotNet" Version="0.15.8" />
+    <PackageReference Include="Microsoft.EntityFrameworkCore.InMemory" Version="10.0.5" />
+    <PackageReference Include="Microsoft.VisualStudio.DiagnosticsHub.BenchmarkDotNetDiagnosers" Version="18.6.37110.2" />
   </ItemGroup>
 
   <ItemGroup>

src/Products/Products.csproj

@@ -11,11 +11,10 @@
     <None Remove="Database.db-wal" />
   </ItemGroup>
   <ItemGroup>
-    <PackageReference Include="System.Text.Json" Version="10.0.3" />
-    <PackageReference Include="System.Formats.Asn1" Version="10.0.3" />
-    <PackageReference Include="Microsoft.EntityFrameworkCore.InMemory" Version="10.0.3" />
-    <PackageReference Include="Microsoft.EntityFrameworkCore.Sqlite" Version="10.0.3" />
-    <PackageReference Include="Microsoft.EntityFrameworkCore.Tools" Version="10.0.3">
+    <PackageReference Include="Microsoft.EntityFrameworkCore.InMemory" Version="10.0.5" />
+    <PackageReference Include="Microsoft.EntityFrameworkCore.Sqlite" Version="10.0.5" />
+    <PackageReference Include="Microsoft.EntityFrameworkCore.SqlServer" Version="10.0.5" />
+    <PackageReference Include="Microsoft.EntityFrameworkCore.Tools" Version="10.0.5">
       <PrivateAssets>all</PrivateAssets>
       <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
     </PackageReference>

src/Products/Program.cs

@@ -7,7 +7,7 @@
 builder.AddServiceDefaults();
 
 // Configure SQL Server connection
-var connectionString = builder.Configuration.GetConnectionString("ProductsDb") 
+var connectionString = builder.Configuration.GetConnectionString("productsdb") 
     ?? "Server=(localdb)\\MSSQLLocalDB;Database=TestDB;Integrated Security=true;TrustServerCertificate=True;";
 
 builder.Services.AddDbContext<ProductDataContext>(options =>

src/README.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-TinyShop is a .NET 9 e-commerce application with:
+TinyShop is a .NET 10 e-commerce application with:
 - **Products API**: Backend API serving product data and images
 - **Store**: Blazor Server frontend for product browsing
 

src/Store.Tests/Store.Tests.csproj

@@ -1,7 +1,7 @@
 <Project Sdk="Microsoft.NET.Sdk">
 
   <PropertyGroup>
-    <TargetFramework>net9.0</TargetFramework>
+    <TargetFramework>net10.0</TargetFramework>
     <ImplicitUsings>enable</ImplicitUsings>
     <Nullable>enable</Nullable>
     <IsPackable>false</IsPackable>