Provide a dotnet global tool version of ilrepack

[kzu]

A dotnet global tool of ilrepack would be much easier to install and use in a cross-platform manner.

This PR provides:

• As-is repackaging of the main executable tool as a dotnet global tool project
• Build and publish (release) workflows that build, test, pack and publish both the original package and the dotnet-tool
• Cross-platform sanity check test for the packaged tool (extensive unit and integration tests aren't strictly necessary since they already run for the main tool and there's no additional code in the dotnet-tool).

The workflows automatically detect and use two repository/org secrets:

• SLEET_CONNECTION: an optional Sleet connection string to provide a CI feed for dogfooding
• NUGET_API_KEY to push both the original package and the dotnet-tool to nuget.org when a release (or prerelease) is created.

An example run of the build workflow can be seen in action at https://github.com/kzu/il-repack/actions/runs/9846710011. And the published CI package for the global tool can be installed with:

dotnet tool install -g dotnet-ilrepack --prerelease --add-source https://kzu.blob.core.windows.net/nuget/index.json

And checked with: ilrepack --version.

[KirillOsenkov]

Thanks! I'll take a look soon. This would fix #289

[ThaDaVos]

Any ETA?

[KirillOsenkov]

I'm very busy these days but I'll try and take a look within a week or two.

[KirillOsenkov]

@kzu I'm not an admin on the repo so I can't set the NUGET_API_KEY to publish. I'm OK with building .nupkg locally and publishing those, since it's infrequent.

Is it the Environment Secret mentioned in the Actions here?

Or maybe @gluck can help us set a secret in the Settings?

[KirillOsenkov]

I uploaded https://www.nuget.org/packages/dotnet-ilrepack/1.0.0 manually for now, could you please try it out?

[MrJul]

Not the OP, but I can confirm that the tool is working fine. Thanks!

[kzu]

@KirillOsenkov it should be the secret in settings, not in env... not sure both map equally 🤔 .

[kzu]

Published package works like a charm. If some day you the nuget secret in the repo, future publishing is just a matter of creating a release (for both packages) 👌