Update all samples to Aspire 13 with net10.0 framework

[Copilot]

Purpose

Updates all samples to use Aspire 13.0.0 with .NET 10 framework and latest compatible packages.

Does this introduce a breaking change?

[x] Yes
[ ] No

Pull Request Type

What kind of change does this Pull Request introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

• Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]

• Test the code

cd base
dotnet build

cd ../byoss
dotnet build

cd ../hostedss
dotnet build

# Repeat for other samples

What to Check

Verify that the following are valid

• All samples build successfully with no errors
• TargetFramework is net10.0 in all project files
• Aspire packages are at version 13.0.0

Package Updates

TargetFramework → net10.0

Aspire packages → 13.0.0

• Aspire.AppHost.Sdk, Aspire.Hosting.AppHost, Aspire.Hosting.Azure.Sql, Aspire.Hosting.SqlServer
• Aspire.Microsoft.Data.SqlClient, Aspire.Microsoft.EntityFrameworkCore.SqlServer
• Aspire.Hosting.NodeJs → Aspire.Hosting.JavaScript (renamed in Aspire 13)

Microsoft.Extensions packages → 10.0.0

• ServiceDiscovery, Http.Resilience, Hosting

OpenTelemetry packages → 1.14.0

• Exporter.OpenTelemetryProtocol, Extensions.Hosting, Instrumentation.*

CommunityToolkit.Aspire packages → 9.9.0

• Hosting.SqlDatabaseProjects, Hosting.Azure.DataApiBuilder, Hosting.NodeJS.Extensions

Dependencies

• Microsoft.EntityFrameworkCore.SqlServer → 10.0.0
• Microsoft.EntityFrameworkCore.Design → 10.0.0
• Microsoft.Data.SqlClient → 6.1.3
• Microsoft.Build.Sql → 2.0.0
• dbup-sqlserver → 6.0.16

Samples Updated

All 8 samples: base, byoss, hostedss, hostedss-dbup, hostedss-dbprj, hostedss-ef, hostedss-dbup-dab, todo_app

Other Information

• Updated README.md to reflect Aspire 13
• Updated deployment command from azd up to aspire deploy in README
• Fixed SQL Database projects (.sqlproj) to use Microsoft.Build.Sql 2.0.0
• Package updates verified using dotnet-outdated -u
• Note: The aspire update CLI command has a bug where --non-interactive still prompts for selection, so manual updates were used instead

Original prompt

update all the samples to use the latest Aspire version

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[yorek]

@copilot update evertyhing to aspire 13 making sure you use the aspire CLI to do the update via "aspire update"
update also all package and references using dotnet-outdate -u
update also the TargetFramework to net10.0

[Copilot]

@copilot update evertyhing to aspire 13 making sure you use the aspire CLI to do the update via "aspire update"
update also all package and references using dotnet-outdate -u
update also the TargetFra...

Done in e548074. Updated all samples to:

• TargetFramework → net10.0
• All Aspire packages → 13.0.0
• Renamed Aspire.Hosting.NodeJs → Aspire.Hosting.JavaScript
• Ran dotnet-outdated -u on all samples (updated EF Core to 10.0.0, dbup-sqlserver to 6.0.16)

Note: The aspire update CLI command has a bug where --non-interactive still prompts for selection, so manual updates were used instead.

[yorek]

@copilot in the readme, instead of mentioning "azd up" I think it is possible to use "azpire deploy", right?

[Copilot]

@copilot in the readme, instead of mentioning "azd up" I think it is possible to use "azpire deploy", right?

Updated in 3cea836. Changed azd up to aspire deploy in the README.

[yorek]

Community contributions do not have packages updated to version 13 yet....