I am not able to advise on either C++ option. However, if your solution doesn't
already use .NET I wouldn't introduce a .NET dependency just for this - just
use the c++ version.
If your solution already contains some .NET classes and your intention is to
add some protobuf, then it perhaps is an option; reflector (insert grumble
about license change) may be of use in providing a translation between c++/cli
=== c#.
Marc
On 5 Jul 2011, at 12:33, jakin lukaszkin...@gmail.com wrote:
Hi
I'm quite new in .net programming. I couldn't find any examples of
using protobuf-net .net classes from c++ code.
I have to write client app working with specified using protobuf
protocol.
And I don't know now If should I wrote it in standard C++ using
protobuf or in C++/CLI using protobuf-net.
If I thinking correctly I should not mix C++/CLI with standard C++ (by
e.g. using protobuf reference implementation).
Unfortunately I could not write in c#.
I will be grateful for any advice!
--
You received this message because you are subscribed to the Google Groups
Protocol Buffers group.
To post to this group, send email to protobuf@googlegroups.com.
To unsubscribe from this group, send email to
protobuf+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/protobuf?hl=en.
--
You received this message because you are subscribed to the Google Groups
Protocol Buffers group.
To post to this group, send email to protobuf@googlegroups.com.
To unsubscribe from this group, send email to
protobuf+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/protobuf?hl=en.
