Skip to content

Remove unsupported DNX-based DARC install instructions - #6538

Merged
dkurepa merged 3 commits into
mainfrom
copilot/remove-incorrect-darc-instructions
Aug 4, 2026
Merged

dkurepa merged 3 commits into
mainfrom
copilot/remove-incorrect-darc-instructions

Conversation

Copilot AI commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

The DARC setup documentation was pointing users to a DNX-based installation flow that does not match the supported client install experience. That guidance was misleading and could lead to failed installs when followed literally.

  • Removed the unsupported dnx tool install and DNX alias instructions from the DARC setup docs.
  • Kept the installation guidance aligned with the supported .NET CLI flow for installing Microsoft.DotNet.Darc.

Copilot AI linked an issue Aug 3, 2026 that may be closed by this pull request
Copilot AI changed the title [WIP] Fix misleading darc install instructions in documentation Remove unsupported DNX-based DARC install instructions Aug 3, 2026
Copilot AI requested a review from dkurepa August 3, 2026 10:54
@dkurepa

dkurepa commented Aug 3, 2026

Copy link
Copy Markdown
Member

@copilot rather than just removing the whole section about using dnx, we should fix it by saying how it's correctly used, we can also give an example, something like dnx --source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-eng/nuget/v3/index.json --prerelease Microsoft.DotNet.Darc -- get-subscriptions

Copilot AI commented Aug 3, 2026

Copy link
Copy Markdown
Contributor Author

@copilot rather than just removing the whole section about using dnx, we should fix it by saying how it's correctly used, we can also give an example, something like ` dnx --source https://pkgs.dev.az...

Updated the doc to describe the correct DNX usage pattern and added an example that runs DARC directly with dnx --source ... --prerelease Microsoft.DotNet.Darc -- get-subscriptions. Commit: 7609241.

@dkurepa
dkurepa marked this pull request as ready for review August 3, 2026 12:07
Copilot AI review requested due to automatic review settings August 3, 2026 12:07

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the DARC client setup documentation to remove misleading/incorrect DNX-based installation guidance and keep the instructions aligned with the supported .NET CLI tool installation flow.

Changes:

  • Removed the unsupported dnx tool install and shell alias guidance from the DARC setup documentation.
  • Added a short example intended to show running DARC without a global tool install (currently still referencing dnx).

Comment thread docs/Darc.md
Comment on lines +144 to 148
If you prefer to run darc without installing it as a global tool, you can use DNX to execute the package directly. For example:

For environments where the standard installation doesn't work, you can use DNX (dotnet execute) to run darc without a global installation:

```
dnx tool install Microsoft.DotNet.Darc --source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-eng/nuget/v3/index.json --prerelease
```

After installation with DNX, you can run darc commands using:

```
dnx Microsoft.DotNet.Darc --help
```

Or create an alias in your shell profile for convenience:

**PowerShell:**
```powershell
Set-Alias -Name darc -Value "dnx Microsoft.DotNet.Darc"
dnx --source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-eng/nuget/v3/index.json --prerelease Microsoft.DotNet.Darc -- get-subscriptions
```
@dkurepa
dkurepa merged commit 82a196c into main Aug 4, 2026
3 of 9 checks passed
@dkurepa
dkurepa deleted the copilot/remove-incorrect-darc-instructions branch August 4, 2026 08:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

darc install instructions are misleading/incorrect

4 participants