Not really, except for convenience; and actually, most of the code-gen in this case is actually done in xslt, not directly in .NET (protogen is very shallow in terms of what it does; most of the code is parsing command-line inputs... it only looks "fat" because it contains an embedded copy of protoc.exe).
Note that the type of codegen that protobuf-net does is a bit different to the codegen in the main branch, so I didn't see any huge advantage in forcing it through that route. Marc --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/protobuf?hl=en -~----------~----~----~----~------~----~------~--~---
