Sdk: Allow including an exe shim for global tools

Created on 6 Feb 2018  路  2Comments  路  Source: dotnet/sdk

Reading through the plan for Global Tools in 2.1, I noticed it mentioned generating an exe shim. It would be useful if there was a way to provide one in the package instead that would be used on Windows.

Question comes down to code signing, namely how can I sign the entry-point of my application? If I can include one or more shims, then those could be signed if the platform supports code signing.

tool

Most helpful comment

Sounds like a great idea. We need to design it and then decide which release it should go in.

All 2 comments

Sounds like a great idea. We need to design it and then decide which release it should go in.

Currently the DotnetToolSettings.xml has options to specify entry point and runner:

<?xml version="1.0" encoding="utf-8" ?>
<DotNetCliTool>
  <Commands>
    <Command Name="demo" EntryPoint="consoledemo.dll" Runner="dotnet" />
  </Commands>
</DotNetCliTool>

Which will generate the "demo" shim.

Maybe something could be done in the future with different (unset?) runners?
non-windows (or even windows?) systems may want to have a symlink generated instead of an executable..

Note that in the NuGet, this is packed under tools\netcoreapp2.1\any\ so in theory, putting in concrete RIDs instead of any could be used to differentiate between runtimes.

Was this page helpful?
0 / 5 - 0 ratings