Skip to content

The option --allow-roll-forward is not documented for dotnet tool install #44614

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
gasparnagy opened this issue Jan 30, 2025 · 5 comments · Fixed by #45147 or #45951
Closed

The option --allow-roll-forward is not documented for dotnet tool install #44614

gasparnagy opened this issue Jan 30, 2025 · 5 comments · Fixed by #45147 or #45951
Assignees
@gewarren
Labels
dotnet-fundamentals/svc in-pr This issue will be closed (fixed) by an active pull request. ⌚ Not Triaged Not triaged

Comments

@gasparnagy
Copy link
Contributor

gasparnagy commented Jan 30, 2025 •
edited by dotnetrepoman bot
Loading

Type of issue

Missing information

Description

The dotnet tool install command seems to have now a --allow-roll-forward option (.NET 9.0.102), but I could not find it in the related documentation page.

The help page of the command contains it already:

Description:
  Install global or local tool. Local tools are added to manifest and restored.

Usage:
  dotnet tool install <packageId> [options]

Arguments:
  <PACKAGE_ID>  The NuGet Package Id of the tool to install.

Options:
  -g, --global                 Install the tool for the current user.
  --local                      Install the tool and add to the local tool manifest (default).
  --tool-path <PATH>           The directory where the tool will be installed. The directory will be created if it does not exist.
  --version <VERSION>          The version of the tool package to install.
  --configfile <FILE>          The NuGet configuration file to use.
  --tool-manifest <PATH>       Path to the manifest file.
  --add-source <ADDSOURCE>     Add an additional NuGet package source to use during installation.
  --source <SOURCE>            Replace all NuGet package sources to use during installation with these.
  --framework <FRAMEWORK>      The target framework to install the tool for.
  --prerelease                 Include pre-release packages.
  --disable-parallel           Prevent restoring multiple projects in parallel.
  --ignore-failed-sources      Treat package source failures as warnings.
  --no-http-cache              Do not cache packages and http requests.
  --interactive                Allows the command to stop and wait for user input or action (for example to complete authentication).
  -v, --verbosity <LEVEL>      Set the MSBuild verbosity level. Allowed values are q[uiet], m[inimal], n[ormal], d[etailed], and diag[nostic].
  -a, --arch <arch>            The target architecture.
  --create-manifest-if-needed  Create a tool manifest if one isn't found during tool installation. For information on how manifests are located, see https://aka.ms/dotnet/tools/create-manifest-if-needed
  --allow-downgrade            Allow package downgrade when installing a .NET tool package.
  --allow-roll-forward         Allow a .NET tool to roll forward to newer versions of the .NET runtime if the runtime it targets isn't installed.
  -?, -h, --help               Show command line help.

Page URL

https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-tool-install

Content source URL

https://github.com/dotnet/docs/blob/main/docs/core/tools/dotnet-tool-install.md

Document Version Independent Id

80822879-4c2e-1c28-ae04-1adb5e7e8a99

Article author

@tdykstra

Metadata

  • ID: 7df78c19-0c6f-fe28-213c-b51dd73398ef
  • Service: dotnet-fundamentals

Related Issues
@dotnet-policy-service dotnet-policy-service bot added the ⌚ Not Triaged Not triaged label Jan 30, 2025
@BartoszKlonowski BartoszKlonowski mentioned this issue Mar 5, 2025
Merged
@dotnet-policy-service dotnet-policy-service bot added the in-pr This issue will be closed (fixed) by an active pull request. label Mar 5, 2025
@gasparnagy
Copy link
Contributor Author

Thank you for the update @BartoszKlonowski and @gewarren.

Sorry for being picky, but I think the PR only fixes the "Options" section of the doc, but not the "Synopsis". Should we also fix that? (I have no permission to reopen the issue.)

@gewarren gewarren reopened this Apr 8, 2025
@gewarren gewarren self-assigned this Apr 8, 2025
@dotnetrepoman dotnetrepoman bot added the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Apr 8, 2025
@dotnet-policy-service dotnet-policy-service bot removed the 🗺️ mapQUEST Only used as a way to mark an issue as updated for quest. RepoMan should instantly remove it. label Apr 8, 2025
@BartoszKlonowski
Copy link
Contributor

@gewarren I see you assigned yourself to this issue. I'm happy to cover the next changes as well, but let me know if your assignment means you will take it from here (as of course I'm totally fine with such option).

@gewarren
Copy link
Contributor

gewarren commented Apr 8, 2025

@BartoszKlonowski Sure, go ahead and make the update, thank you.

@gewarren
Copy link
Contributor

@BartoszKlonowski Do you still plan to work on this?

@BartoszKlonowski
Copy link
Contributor

@gewarren Yes, sorry for the delay. Of course, changes will be delivered within three hours.

@BartoszKlonowski BartoszKlonowski mentioned this issue Apr 29, 2025
Merged
@github-project-automation github-project-automation bot moved this from 🔖 Ready to ✅ Done in dotnet/docs April 2025 sprint project Apr 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gewarren gewarren

Labels
dotnet-fundamentals/svc in-pr This issue will be closed (fixed) by an active pull request. ⌚ Not Triaged Not triaged
Projects
No open projects
dotnet/docs April 2025 sprint project
Status: ✅ Done
Milestone
No milestone
3 participants
@gasparnagy @gewarren @BartoszKlonowski