Fix Docker build: resolve NU1510 warnings and missing dotnet-ef tool

[Copilot]

Docker container was crash-looping due to missing dotnet-ef tool during migrations. Build also generated 6 NU1510 warnings for redundant package references.

Changes

Removed redundant package references from Melodee.Blazor.csproj

• Eliminated 6 Microsoft.Extensions.* packages already provided by ASP.NET Core 10 shared framework
• Resolves all NU1510 warnings

Fixed dotnet-ef tool installation in Dockerfile

• Removed premature installation from build stage (before package restore)
• Added versioned installation --version 10.0.1 matching EF Core dependencies
• Installed after user creation with proper PATH configuration

Added Directory.Build.props to Docker image

• Copied to both build and final stages
• Required for AllowMissingPrunePackageData MSBuild property during migrations

Verification

$ dotnet restore
# 0 warnings (previously 6 NU1510 warnings)

$ dotnet build -c Release
# 0 warnings, 0 errors

$ dotnet test -c Release
# 1231 passed, 1 skipped

Container should now start successfully and execute migrations without the "dotnet-ef does not exist" error.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• http://s.symcb.com:443/universal-root.crl
  • Triggering command: /usr/bin/dotnet dotnet restore --verbosity detailed (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Melodee Docker Issues</issue_title>
<issue_description>app_logs.txt
User reported this issue via Discord:

The build process completes successfully, however the melodee app service keeps restarting. From the logs it seems to me that this might be related to .net 10.0 as well.
I attached the logs of the db and the main app. Hope they can be useful.
</issue_description>

<agent_instructions>Review the attached log. Review the DockerFile. Review the solution. Then 1. Resolve "warning NU1510:" warnings, do not add ignore, resolve the issue that is causing the warning. 2. Resolve the errors about missing dotnet-ef core "You intended to execute a .NET program, but dotnet-ef does not exist.". </agent_instructions>

Comments on the Issue (you are @copilot in this section)

@sphildreth Validated issue; I was able to reproduce error setting up demo site.

• Fixes Melodee Docker Issues #37

---

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

[sphildreth]

@copilot Is this going to break the build? Ensure all projects in solution build. Do a "dotnet clean" then "dotne build". Ensure all unit tests pass.

[Copilot]

Verified - the changes do not break the build. All validation complete:

✅ dotnet clean - successful
✅ dotnet build - 0 warnings, 0 errors (all 6 projects built successfully)
✅ dotnet test - 3016 passed, 1 skipped, 0 failed
✅ dotnet restore - 0 warnings (NU1510 warnings eliminated)

The removed package references are indeed redundant - they're already provided by the ASP.NET Core 10 shared framework and are properly resolved transitively.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• itunes.apple.com
  • Triggering command: /usr/share/dotnet/dotnet /usr/share/dotnet/dotnet exec --runtimeconfig /home/REDACTED/work/melodee/melodee/tests/Melodee.Tests.Common/bin/Debug/net10.0/Melodee.Tests.Common.runtimeconfig.json --depsfile /home/REDACTED/work/melodee/melodee/tests/Melodee.Tests.Common/bin/Debug/net10.0/Melodee.Tests.Common.deps.json /home/REDACTED/work/melodee/melodee/tests/Melodee.Tests.Common/bin/Debug/net10.0/testhost.dll --port 38981 --endpoint 127.0.0.1:038981 --role client --parentprocessid 3837 --telemetryoptedin false (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[Copilot]

Pull request overview

This PR resolves Docker container crash-looping issues by fixing missing dotnet-ef tool installation and eliminating redundant package reference warnings. The changes ensure the container can successfully execute EF Core migrations and start the application without errors.

Key Changes:

• Removed 6 redundant Microsoft.Extensions.* package references that are already included in ASP.NET Core 10 shared framework, eliminating NU1510 warnings
• Fixed dotnet-ef tool installation by moving it after user creation and adding explicit version pinning (10.0.1) to match EF Core dependencies
• Added Directory.Build.props to Docker image to support MSBuild properties required during migrations

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/Melodee.Blazor/Melodee.Blazor.csproj	Removed 6 redundant Microsoft.Extensions package references that caused NU1510 warnings
Dockerfile	Fixed dotnet-ef tool installation timing and version, added Directory.Build.props copying to both build and final stages

The changes are well-structured and properly address both reported issues. The removal of redundant package references is correct since ASP.NET Core 10 already includes these packages in the shared framework. The dotnet-ef tool installation fix properly sequences the installation after user creation and pins to the correct version matching the EF Core dependencies.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.