Installing tool to custom tool-path fails when trying to access it

I’m trying to install a custom tool during azure pipeline however if fails to pick up the tool. I’ve tried several options but they all fail at execution stage. I’m trying to use the tool-path because without it step 2 fails with cannot find the executable

Steps to reproduce

- task: DotNetCoreCLI@2
  displayName: 'Install Stryker'
  continueOnError: true
  inputs:
    command: custom
    custom: tool
    vstsFeed: ${{ parameters.Build_Vsts_Feed }}
    arguments: 'install dotnet-stryker --tool-path ~/tools'

- script: |    
    cd ${{ parameters.Unit_Test_Folder }}
    dotnet ~/tools/stryker --project-file=${{ parameters.Stryker_Project }}.csproj
  displayName: 'Run Stryker tests against ${{ parameters.Stryker_Project }}'

Expected behavior

Tool should install and be executable

Actual behavior

Output from Installation task

sr/bin/dotnet tool install dotnet-stryker --tool-path ~/tools 
You can invoke the tool using the following command: dotnet-stryker |  
Tool 'dotnet-stryker' (version '0.11.0') was successfully installed.

Output from execution task No executable found matching command "dotnet-/home/vsts/tools/stryker"

No matter how i define tool-path it does the above behaviour of merging dotnet- to the path rather than /home/vsts/tools/dotnet-stryker

[livarcocc]

@wli3 can you take a look?

[vincentvanderwalt]

@wli3 Thank you for the response. I can confirm it’s now working for me. Much appreciated