AzureSignTool
AzureSignTool copied to clipboard
README.md is out of sync with current state of your project
Your last release appears to have completely dropped the EXE implementation and gone with a Nuget "global tool" version. Your README still mentions the EXE as if it were the only way to access. Someone downloading your latest package and attempting to use your README (which is, by the way, the only documentation I have been able to find) will be greatly confused.
My confusion appears to stem from my attempts to use the AzureSignTool nuget distribution package outside the nuget distribution mechanism. When installed via dotnet tool install
, the nuget global tool package somehow generates an EXE and stores it in an arbitrary location outside the normal system path. So, once you've installed and configured the DotNetCore SDK and have the installation location in your PATH variable, things appear to work as documented. It looks like minor documentation enhancements would be a great help.
IMHO, making the only method of installing and using the latest version of this tool completely reliant on dotnet tool install
is a step backwards. I would urge you to support a direct installation approach, as well. Not everyone who wants to utilize this very useful tool is doing it with dotnetcore in mind.
First, apologies for the much belated reply.
It looks like minor documentation enhancements would be a great help.
You're right; some improvements to the documentation on installing would probably help a lot here.
I would urge you to support a direct installation approach, as well.
I agree. The next release will publish single-file executables.
The history there is that in the .NET Core 2.x days; there was no single file option, and there was no self-contained installation. So at minimum, you would have needed the .NET Core Runtime installed anyway, which lead to some confusion. All of that is fixed in .NET Core 3 now, so I feel comfortable going back to supporting stand-alone EXE downloads.
I'm going to leave this issue open until I have actually addressed all of these and have made a new release, which I expect to soon, but thought I would share my plan.
Thanks, I was having the same problem until I came in here and saw this thread. Compiled and was looking for .exe everywhere.