Thanks you nailed it. I thought the generated proto file was the same but
they were slightly different between the C++ and C# repositories I was
working with. This will get me to use git submodule. Thanks again.
On Wed, 4 Jan 2017 at 15:05 Tim Kientzle wrote:
>
> On Jan 4,
> On Jan 4, 2017, at 11:57 AM, Jamie Sherman wrote:
>
> So I forced the message to have fixed values:
>
> C#
> xsetHeader.TotalXicSets = 10;
> xsetHeader.WiffName = "myWiffNameHolder";
>
> hexdump of message:
>
>
On Wed, Jan 4, 2017 at 11:57 AM Jamie Sherman
wrote:
>
>
> On Wednesday, 4 January 2017 14:36:04 UTC-5, Feng Xiao wrote:
>
>
>
> On Wed, Jan 4, 2017 at 8:38 AM, Jamie Sherman wrote:
>
> I have a proto message that I have defined. I'm consuming the
On Wednesday, 4 January 2017 14:36:04 UTC-5, Feng Xiao wrote:
>
>
>
> On Wed, Jan 4, 2017 at 8:38 AM, Jamie Sherman > wrote:
>
>> I have a proto message that I have defined. I'm consuming the message on
>> OSX using C++ and producing it on windows using C#.
>> I'm using
On Wed, Jan 4, 2017 at 8:38 AM, Jamie Sherman
wrote:
> I have a proto message that I have defined. I'm consuming the message on
> OSX using C++ and producing it on windows using C#.
> I'm using release 3.0.0 of Google.protobuf (NuGet on windows, compiled and
> built on
I have a proto message that I have defined. I'm consuming the message on
OSX using C++ and producing it on windows using C#.
I'm using release 3.0.0 of Google.protobuf (NuGet on windows, compiled and
built on OSX).
I have read that Protobuf stores UTF-8 strings. I realize that native C#