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 prot
Not 100% on-topic, but: is there any special reason why the code
generator for .NET needs to be written in .NET itself? The Java
generator isn't written in Java, after all. We've been using
Jon's .NET library, and we just copy-and-pasted the standard Java
generator and made a C# generator for p
Not 100% on-topic, but: is there any special reason why the code
generator for .NET needs to be written in .NET itself? The Java
generator isn't written in Java, after all. We've been using
Jon's .NET library, and we just copy-and-pasted the standard Java
generator and made a C# generator for p
> Nice work - makes my port look somewhat hard work :)
The source is fully available, so feel free to look at how it hangs
together; you'll need to get your own VSIP key, of course.
> If I can ever call the native protoc library using P/Invoke
If you figure that one out, let me know - I'm curre
On Jul 16, 10:02 am, Marc Gravell wrote:
> I'm happy to say that protobuf-net now features VS2008 integration.
> Please see the following page for more
> information:http://marcgravell.blogspot.com/2009/07/protobuf-net-now-with-added-o...
Nice work - makes my port look somewhat hard work :) If
I'm happy to say that protobuf-net now features VS2008 integration.
Please see the following page for more information:
http://marcgravell.blogspot.com/2009/07/protobuf-net-now-with-added-orcas.html
Marc Gravell
(protobuf-net)
--~--~-~--~~~---~--~~
You received thi
