[docs] Document in-process NuGet operations and credential provider support - #1731
aspire-repo-bot[bot] wants to merge 1 commit into
Conversation
…(aspire#19847) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
| <Aside type="note"> | ||
| Aspire 13.6 and later run bundled NuGet search and restore in-process | ||
| instead of through a separate `aspire-managed` helper, and initialize | ||
| NuGet's credential service so installed credential provider plugins are | ||
| used. If a feed still returns `401` after updating, confirm the | ||
| credential provider plugin (for example, the Azure Artifacts Credential | ||
| Provider) is installed and can authenticate outside Aspire, such as with | ||
| `dotnet nuget locals`. | ||
| </Aside> | ||
|
|
There was a problem hiding this comment.
This is
| <Aside type="note"> | |
| Aspire 13.6 and later run bundled NuGet search and restore in-process | |
| instead of through a separate `aspire-managed` helper, and initialize | |
| NuGet's credential service so installed credential provider plugins are | |
| used. If a feed still returns `401` after updating, confirm the | |
| credential provider plugin (for example, the Azure Artifacts Credential | |
| Provider) is installed and can authenticate outside Aspire, such as with | |
| `dotnet nuget locals`. | |
| </Aside> |
|
This is unnecessary - no user facing change here. |
Frontend HTML artifact readyThe latest frontend build uploaded the This comment updates automatically when a new frontend build artifact is uploaded. |
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
Replace the dotnet nuget locals diagnostic with an operation that actually tests feed authentication.
Get a fresh assessment by requesting another Copilot review.
Review effort: Lite
Findings: 1
Open (1)
What changed in this PR
This docs-only PR documents Aspire 13.6’s in-process NuGet operations and credential-provider support.
Changes:
- Adds release-note coverage for the CLI changes.
- Updates Azure Artifacts troubleshooting guidance.
| File | Description |
|---|---|
src/frontend/src/content/docs/whats-new/aspire-13-6.mdx |
Documents in-process NuGet behavior and credential providers. |
src/frontend/src/content/docs/get-started/troubleshooting.mdx |
Adds Azure Artifacts troubleshooting guidance. |
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| used. If a feed still returns `401` after updating, confirm the | ||
| credential provider plugin (for example, the Azure Artifacts Credential | ||
| Provider) is installed and can authenticate outside Aspire, such as with | ||
| `dotnet nuget locals`. |

Documents changes from microsoft/aspire#19847.
@eerhardtTarget:
release/13.6, based on the source PR milestone13.6(exact match:release/13.6already exists onmicrosoft/aspire.dev).Why
Source PR microsoft/aspire#19847 moves bundled Aspire CLI NuGet operations (search, restore, package probe-manifest generation) from a separate
aspire-managed nugetsubprocess into the Native AOTaspireexecutable, calling NuGet.Client APIs in-process. This is a user-facing change:aspire integration listandaspire addkeep working without startingaspire-managed).aspire-managedhelper never initialized NuGet's credential service, so bundled search/restore could only use credentials stored innuget.config. Feeds that rely on a credential provider plugin (for example, Azure Artifacts) returned401. The in-process client now initializes the credential service, so installed credential provider plugins are used.The PR body's "User-facing usage" and "Intentional behavior change: NuGet credential providers" sections both describe user-visible effects, which triggered the
pr_body_has_user_facing_sectionandpr_body_has_cli_flag_mentionsignals (the latter from the--nuget-configfallback discussion). No existing docs mentioned this fix by name, so this PR documents it.What changed
src/frontend/src/content/docs/whats-new/aspire-13-6.mdx: added a new "In-process NuGet operations, with credential provider support" subsection under "🛠️ Aspire CLI enhancements", explaining the removal of theaspire-managedsubprocess hop for NuGet operations and the credential provider plugin fix. Also updated the release summary bullet to mention it.src/frontend/src/content/docs/get-started/troubleshooting.mdx: added a note to the existing "aspire addfinds no packages with an Azure Artifacts feed" troubleshooting entry, clarifying that 13.6+ initializes the NuGet credential service and how to further diagnose a persistent401after updating.Both are updates to existing pages — no new pages were created.