> - Improved code generation, including running protoc automatically,
> providing options on the command line instead of in the proto file,
> and removing the options dependency from the generated code
A thought on that:
I was looking at Marc's generator today to figure out how to get a --
proto_path argument passed through from the CustomTool runner in
Visual Studio. Unless I'm missing something, it appears that VS
doesn't provide a very nice way to get arguments to a custom tool on a
per-file basis. He is using the "Custom Tool Namespace" property to
piggyback in arguments to the code generator. From a usage perspective
this is fairly messy but I couldn't find a better way to do it. I
thought at the time that if it were possible to specify custom options
directly in the file (like dotnet-protobufs) it would be a whole lot
cleaner.
Having the command line option is probably better for a build script
generating the files, but if you ever package it up into a custom tool
for VS, it might be nice to still be able to specifying the options in
the file.
-Thad