Stop releasing Microsoft.ComponentDetection nuget package

[thompson-tomo]

Due to the current build process a package is being created for the Microsoft.ComponentDetection project however this project is producing a cli tool and as such it shouldn't be released as a library.

The package should not be produced going forward and the already listed package should be unlisted from nuget.org.

[martincostello]

Why not instead keep creating the NuGet package, but turn it into a .NET global tool?

Then it can be distributed via NuGet and consumed from the .NET SDK such as:

> dotnet tool install Microsoft.ComponentDetection --global 
> dotnet ComponentDetection scan --SourceDirectory MyProject

That would be preferrable to the default instructions in the README to clone the whole repo and build it from source to run it (which is what I just did).

[thompson-tomo]

sure that would be another option, i did however think that is what https://www.nuget.org/packages/Microsoft.Sbom.DotNetTool is for and would rather have 1 tool

[martincostello]

I assume that's an unrelated tool because it's from a completely different repository: https://github.com/microsoft/sbom-tool, unless that tool uses ComponentDetection itself.

[thompson-tomo]

Just checked and the sbom tool does in fact look like the sbom tool uses the component detector libraries.

[martincostello]

Still, if someone wants to specifically use this tool, a .NET tool would be an improvement on the current acquisition paths (clone and build or download a platform-specific binary) for .NET users.