Binary sn.exe is not provided by .Net Core SDK 2.1.302 on unix (but it is by mono...)
IMHO dotnet/cli should be a standalone replacement for mono (when migrating to netstandard2.0/netcoreapp2.1) so needing mono to get the sn.exe binary to be able to sign seems odd to me...
My current workaround is to create a CreateSigningKey.csproj project targeting netcoreapp2.1 (since there are issue on unix with relative path Directory.GetCurrentDirectory() in netcoreapp2.0 dotnet/cli#9319 -_-) to generate the key without depending on mono (or Visual Studio)
cf: https://github.com/google/or-tools/tree/v6.8/tools/dotnet/CreateSigningKey
usage: dotnet run --project CreateSigningKey/CreateSigningKey.csproj foo.snk
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
A virtual machine (VM) is an embedded computer used to separate runtimes or run different operating systems.
@Backup-eric645 needing a docker with mono installed just to run the sn.exe to be able to sign a simple project under a unix machine is not an option IMHO.
Most helpful comment
@Backup-eric645 needing a docker with mono installed just to run the sn.exe to be able to sign a simple project under a unix machine is not an option IMHO.