Create dotnet global tool for command line users

[drewnoakes]

For example:

dotnet new console -o mex

<ToolCommandName>mex</ToolCommandName>
<PackAsTool>true</PackAsTool>

dotnet build
dotnet pack
# create local package repo for testing
dotnet new nugetconfig

<configuration>
 <packageSources>
    <clear />
    <add key="nuget.org" value="https://api.nuget.org/v3/index.json" protocolVersion="3" />
    <add key="local" value="d:/nuget-local" />
 </packageSources>
</configuration>

dotnet tool install -g mex
mex file.jpg

Include installation/update instructions in README for users who just want to view metadata rather than program against the API.

[oliver021]

It's a great idea, the question is the pattern to follow for the cli application, that is, we need to know what parameters it would have, or subcommands, I have used a third-party library to build a CLI application with the best practices. Let's say you trivialize the task of defining the application's flags and commands in help and achieve it with an aspect-oriented paradigm in your code.