New mpc(MessagePackCompiler)

[neuecc]

completely new code-generator.

-i, -input: Input path of analyze csproj or directory, if input multiple csproj split with ','.
-o, -output: Output file path(.cs) or directory(multiple generate file).
-c, -conditionalSymbol: [default=null]Conditional compiler symbols, split with ','.
-r, -resolverName: [default=GeneratedResolver]Set resolver name.
-n, -namespace: [default=MessagePack]Set namespace root name.
-m, -useMapMode: [default=False]Force use map mode serialization.
-ms, -multipleIfDiretiveOutputSymbols: [default=null]Generate #if-- files by symbols, split with ','.

may solves #355, #386.

Currently this implementation is very poor.
But especialy new directory input works fine on Unity(maybe).

You can try binary from here: https://www.dropbox.com/s/4nj90rrx7lsu70v/MessagePackCompiler.zip?dl=0
(19-02-26 17:52(JST) update, support valuetuple, output dir modified)

[jsteinich]

I hit a couple issues using this.

1. A type that exists in a reference library ended up being not fully qualified in the generated code. This was a build error. If it makes any difference, the type was in a parent class containing unions of its subclasses.
2. Formatters aren't being generated for types that exist in a referenced project. It happens to be that all of the missing types are enums, but it also just happens that those are the only types referenced. There are no build time errors for this.

[neuecc]

thanks for reporting, i'll investigate it.

[jsteinich]

I got a chance to take another look at this and it still has issues. Looking at the code it makes sense as there is a TODO to implement package references.
Looking at how to do that seems to end up with something very similar to what the universal code generator is doing.

I'm curious which version of the code generator is intended to be used going forward.

[AArnott]

Is this obsolete by #591?

[neuecc]

yes, now ported to #591.