-
Notifications
You must be signed in to change notification settings - Fork 488
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.
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
Document dotnet tools plugin usage #3379
base: main
Are you sure you want to change the base?
Conversation
Learn Build status updates of commit 18ce1c9: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Learn Build status updates of commit eba36da: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Learn Build status updates of commit 7de8612: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
|
||
1. Plugins installed as .NET tools must follow a naming convention: **`nuget-plugin-*`**. | ||
2. Upon installation, these plugins are added to the `PATH` by the .NET SDK. NuGet scans the `PATH` environment variable for executables with names starting with `nuget-plugin-`. | ||
3. On Windows, NuGet looks for `.exe` or `.bat` files, while on Linux and macOS, it identifies plugins by checking for the executable bit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this in addition to #1?
So how does one ship a global tool that works on both linux & windows?
Fixes: NuGet/Home#13858