Bernhard Richter

What if you change this line https://github.com/filipw/dotnet-script/blob/60de06f07cfc4e4be34a5cef7168741126d00acc/install/install.ps1#L24 into ``` $paths = $path.Split(";") -inotlike "*dotnet-script*" ``` Does it work as expected then?

We should maybe consider scaffolding the shebang on *nix. We already set up the `omnisharp.json` during `dotnet script init` so OmniSharp will be happy either way

@tomlm @filipw This is something I have been wanting for a long time. never had the time to look into it. Would be super useful 👍 > dotnet script tool...

@tomlm Let us know if you're taking a stab at this. Otherwise I might start looking into it 😎

I agree that we should provide some kind of feedback, although we must be careful not to clutter the standard output here as that would cause trouble in piping scenarios....

`stderr` can be used for diagnostics so I guess it's a philosophical question whether `dotnet restore` output can be seen as diagnostics 😃

Okay, so we already do logging to `stderr` Glad I had this conversation with myself 😄 . So given that we should display anything in the console, should we always...

That might work. We could probably also simply project the state of the resolver so that we can continue to do the `PortableExecutionReference` hack until it is resolved in Roslyn....

@BryanWilhite A lot of water under the bridge since 0.13.0. Appreciate if you could see if this works as expected with the latest version 👍

Please note that you need the .Net Core 2.1 SDK to use global tools