mirrors/dotnet-installer
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

minor changes in numbering in Adding a command section

Browse source
This commit is contained in:
Ravi Mandal 2017-04-03 23:18:12 +05:45 • committed by GitHub
parent 4145c3304d
commit 1af5dc236f
1 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
Documentation/project-docs/developer-guide.md
View file

@ -44,10 +44,10 @@ Using the `dotnet` built in the previous step:
The dotnet CLI supports several models for adding new commands: The dotnet CLI supports several models for adding new commands:
0. In the CLI itself via `dotnet.dll` 1. In the CLI itself via `dotnet.dll`
1. Through a `tool` NuGet package 2. Through a `tool` NuGet package
2. Through MSBuild tasks & targets in a NuGet package 3. Through MSBuild tasks & targets in a NuGet package
3. Via the user's `PATH` 4. Via the user's `PATH`
### Commands in dotnet.dll ### Commands in dotnet.dll
Developers are generally encouraged to avoid adding commands to `dotnet.dll` or the CLI installer directly. This is appropriate for very general commands such as restore, build, publish, test, and clean, but is generally too broad of a distribution mechanism for new commands. Please create an issue and engage the team if you feel there is a missing core command that you would like to add. Developers are generally encouraged to avoid adding commands to `dotnet.dll` or the CLI installer directly. This is appropriate for very general commands such as restore, build, publish, test, and clean, but is generally too broad of a distribution mechanism for new commands. Please create an issue and engage the team if you feel there is a missing core command that you would like to add.