[Bug] Version numbers and behavior are inconsistent between the releases page and NuGet (dotnet tool)

[NightOwl888]

Describe the bug
A clear and concise description of what the bug is.

Behavior and version numbering is different between downloading the dotnet tool and downloading the compiled release on the releases page.

To Reproduce
Steps to reproduce the behavior:

1. Install the dotnet tool dotnet tool install -g docfx. It says it installed the latest version (in my case 2.75.2)
2. Run docfx --version. It displays the version as 2.56.2.
3. Download the zip package from the Releases page 2.75.2.
4. Unzip and run docfx --version. It displays 2.75.2+fe673ecea2ac444a4fd480e6cfcf605c78614385.
5. Run docfx --help in each environment. The download from the Releases page displays much more detail than the dotnet tool.

Dotnet Tool

Executable from 2.75.2 release

Expected behavior

The behavior of the tools is the same and they report the same version number. It is unclear what version the dotnet tool is. It appears to be older because it doesn't even display the same --help menu that the zip file from the Releases page does. If it at least reported the correct version number, I wouldn't worry about it.

Context (please complete the following information):

• OS: Windows 10 x64
• Docfx version: 2.75.2 (or at least that is what I want)

Additional context
None

[filzrev]

What's the result when you run the following commands.

where docfx

It's expected to be %USERPROFILE%\.dotnet\tools\docfx.exe.

If other exe path are displayed. It need to confirm PATH settings.
(It is caused when previously installed docfx with chocolatey/scoop)

[NightOwl888]

Thanks. You were right, I had a previously installed version of docfx via chocolatey that I didn't recall.

>where docfx
C:\ProgramData\chocolatey\bin\docfx.exe
C:\Users\shad\.dotnet\tools\docfx.exe

I had to fuss with it for awhile because the uninstall command for chocolatey failed, then I had to delete the files, install it again, and uninstall it again to clean up everything.

But after doing that and reinstalling the latest version, I am now seeing the correctly reported version from the command prompt.

On a side note, we are having some issues upgrading due to missing command options, some deprecated dependencies, and plugins that no longer function. apache/lucenenet#911. Is there an upgrade guide, or could you please chime in to help get us through some of the hoops of upgrading?