PackAsTool / ToolCommandName

[jzabroski]

@KirillOsenkov Given the inputs to Program.cs are hardcoded (#52), once this is fixed, it makes sense to package RoslynQuoter as a .NET Core CLI Tool. Doing would also therefore require packaging it as a netcoreapp3.1 TargetFramework in additional to legacy .NET Framework.

RoslynQuoter/src/Quoter/Quoter.csproj

Lines 3 to 7 in f218513

	<PropertyGroup>
	<AssemblyName>RoslynQuoter</AssemblyName>
	<OutputType>Library</OutputType>
	<TargetFramework>netstandard2.0</TargetFramework>
	</PropertyGroup>

Suggested XML:

<PropertyGroup Condition=" '$(TargetFramework)' == 'netcoreapp3.1' ">
  <PackAsTool>true</PackAsTool>
  <ToolCommandName>dotnet-quote</ToolCommandName>
</PropertyGroup>

[GrahamTheCoder]

In case someone works on this, if you want to support loading files from .NET Framework projects, you can copy what I did in the ICSharpCode CodeConverter:
https://github.com/icsharpcode/CodeConverter/pull/556/files#diff-f0ba4035427169d7318d6227b74de3e8R25
Basically check if there's a Visual Studio MSBuild version, and if so, start a framework process and redirect the output back to the core app.
Thanks for the great tool Kirill!