-
Notifications
You must be signed in to change notification settings - Fork 6.1k
sn.exe not available on unix #7183
Copy link
Copy link
Closed
Labels
📌 seQUESTeredIdentifies that an issue has been imported into Quest.Identifies that an issue has been imported into Quest.dotnet-framework/svcin-prThis issue will be closed (fixed) by an active pull request.This issue will be closed (fixed) by an active pull request.
Description
Activity
Metadata
Metadata
Assignees
Labels
📌 seQUESTeredIdentifies that an issue has been imported into Quest.Identifies that an issue has been imported into Quest.dotnet-framework/svcin-prThis issue will be closed (fixed) by an active pull request.This issue will be closed (fixed) by an active pull request.
Type
Projects
- StatusShow more project fields✅ Done
Binary
sn.exeis not provided by.Net Core SDK 2.1.302on 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.exebinary to be able to sign seems odd to me...My current workaround is to create a
CreateSigningKey.csprojproject targetingnetcoreapp2.1(since there are issue on unix with relative pathDirectory.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.snkDocument Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
Associated WorkItem - 558442