Use a custom MSBuild task

This will replace the use of the Exec task to run MinVer.dll as an executable, with the use of a custom task within that assembly. This is dependent on either #256, or changes in LibGit2Sharp which @bording is aware of.

One functional effect of this change is that the MSBuild verbosity level will be respected, which means that MinVerVerbosity will be ignored (probably deprecated initially, with a warning message). This could be considered a breaking change. It will also mean that the calculated version will not be outputted to the console (when the MSBuild verbosity level is detailed) as a side effect of using the Exec task.

[bording]

involves managing System.Process requires listening to stderr and parsing (I’m not sure how reliable this is)

There is a ToolTask type that would be worth looking at to see if it helps with these.

requires another project sitting between MinVer and MinVer.Lib, and more complex packaging

It seems like it could be possible to use the minver-cli output instead of needing a separate project.

[bording]

The fact that there is no way to know the configured log level is rather annoying.

I agree with your assessment that it doesn’t make sense to go ahead and try for a task now just to get rid of MinVerVerbosity.

I’d say this can wait until it’s feasible to actually use LibGit2Sharp directly from an MSBuild task.