[✨ Triage] dotnet/aspire#10175 by JamesNK - NU1510 on my machine after .NET 10 SDK update

[MihuBot]

Triage for dotnet/aspire#10175.
Repo filter: area-dashboard issues.
MihuBot version: 4431de.
Ping MihaZupan for any issues.

This is a test triage report generated by AI, aimed at helping the triage team quickly identify past issues/PRs that may be related.
Take any conclusions with a large grain of salt.

dotnet/aspire#10175: NU1510 on my machine after .NET 10 SDK update by JamesNK
[Tool] Searching for NU1510, Warning As Error: PackageReference will not be pruned, Microsoft.Extensions.FileProviders.Embedded, pruned package reference, Aspire .NET 10 SDK update, NU1510 after SDK update (IncludeOpen=True, IncludeClosed=True, IncludeIssues=True, IncludePullRequests=True, Repository=dotnet/aspire)
[Tool] Found 146 issues, 207 comments, 146 returned results (18396 ms)

Here are the most relevant related issues and discussions for issue #10175, "NU1510 on my machine after .NET 10 SDK update":

---

1. Issue #5061 (July 2024) - Build failing because of a nuget warnings for Microsoft.FluentUI.AspNetCore.Components 4.9.2

• Summary: This issue discusses build failures due to NuGet warnings being treated as errors, specifically for a package that is not trusted or not timestamped. While the error code is different (NU3018/NU3027), the context is similar: NuGet warnings as errors after SDK or package updates.
• Conclusion: The discussion suggests that some warnings are new or more strictly enforced in newer SDKs, and that updating or removing unnecessary package references can help. The package in question was updated to a newer version to resolve the issue.

---

2. Issue #1253 (December 2023) - Adding Aspire Orchestration Causes Errors When Using Directory.Packages.props

• Summary: This issue is about errors when using central package management and Aspire, with NuGet errors about how versions are specified. The root cause is a mismatch between how package versions are managed and how Aspire templates specify them.
• Conclusion: The problem is not unique to Aspire and is tracked by NuGet. The workaround is to ensure package versions are managed centrally and not duplicated in csproj files.

---

3. Issue #1477 (December 2023) - Following Latest build instructions results in NU1507 Message about 2 package sources defined when using CPM

• Summary: This issue is about NuGet warnings as errors (NU1507) when using central package management and multiple package sources. While not the same error code, it is a similar class of problem: NuGet warnings as errors due to project/package configuration.
• Conclusion: Workarounds include adjusting NuGet.config or disabling certain features. There is also a mention that Aspire SDK installation can trigger these warnings.

---

4. Issue #6765 (November 2024) and #7878 (March 2025) - Dashboard/Blazor issues after updating to .NET 10 SDK

• Summary: These issues are about Aspire projects breaking after updating to .NET 10 SDK, including missing resources and blank dashboards. While not about NU1510, they show that Aspire projects may need updates to work with .NET 10 SDK, and that some package references or resource handling may need to be revisited.
• Conclusion: The root cause was changes in how resources are handled in .NET 10, and the solution was to update Aspire to a version compatible with .NET 10 or to update how resources are embedded and referenced.

---

5. PR #10075 (June 2025) - Update to .NET 10 SDK and Arcade 10

• Summary: This PR is the update that moved Aspire to .NET 10 SDK. The discussion includes concerns about compatibility, build/test validation, and the need to update package references and project files to align with new SDK behaviors.
• Conclusion: After the update, some issues were expected and discussed, including the need to clean up or remove unnecessary package references that may now trigger warnings or errors.

---

6. General context on NU1510

• What is NU1510?
  NU1510 is a NuGet warning (which can be treated as an error) indicating that a PackageReference will not be pruned and is likely unnecessary. This often happens when a package is referenced but not actually used, or when SDK/package logic changes how dependencies are resolved and pruned.
• Typical solution:
  Remove the unnecessary PackageReference from your project file. In this case, Microsoft.Extensions.FileProviders.Embedded is likely not needed and can be safely removed from Aspire.Dashboard.csproj.

---

Summary and Recommendation

• Your issue is a direct result of stricter NuGet warning enforcement in the .NET 10 SDK.
• The referenced package (Microsoft.Extensions.FileProviders.Embedded) is likely not needed and can be removed from your project file.
• This is a common class of issue after SDK updates, as seen in other issues and PRs.
• No other Aspire-specific issues mention NU1510 directly, but similar problems have been resolved by cleaning up unnecessary or legacy package references.

---

Action:
Remove the PackageReference to Microsoft.Extensions.FileProviders.Embedded from Aspire.Dashboard.csproj unless you have a specific reason to keep it. This should resolve the NU1510 error.

If you need to keep the reference for some reason, you can suppress the warning, but the preferred solution is to remove unused package references.

---

References:

• Issue #5061
• Issue #1253
• Issue #1477
• Issue #6765
• Issue #7878
• PR #10075

Let me know if you need more details on any of these related issues!