Are you using the FieldMask as a way of performing an update? If so, I
believe you would want to use FieldMaskUtil::MergeMessageTo() to update the
fields indicated in the mask. That way, you don't have to manually check
which paths are present.
On Wed, Oct 25, 2017 at 6:15 PM, Antonia Elsen
Thanks, I tested a single file and it works.
I am new to this, I have another question. If I have several proto files,
and some of them have a line "import xxx.proto;", which refers to many
other proto files, do I need to compile each of these .proto in any
particular order?
El viernes, 27
protobuf-net should work with proto 2 - try here:
https://protogen.marcgravell.com
On 27 Oct 2017 6:16 p.m., "cleal" wrote:
> I have to integrate a third part protocol from a gps device, they send me
> the .proto files, they are using the schema proto2.
>
> I should
On Fri, Oct 27, 2017 at 10:16 AM, cleal wrote:
> I have to integrate a third part protocol from a gps device, they send me
> the .proto files, they are using the schema proto2.
>
> I should receive the binary messages and I need desarialize it in order to
> work with the
I have to integrate a third part protocol from a gps device, they send me
the .proto files, they are using the schema proto2.
I should receive the binary messages and I need desarialize it in order to
work with the location data. But I see in forums that C# only works for
proto3. There is
Oh, if all you're worried about is compatibility then I would definitely
upgrade to the latest version (currently 3.4.1). We take great care to
preserve wire format compatibility and so all your existing serialized
messages will be readable with the latest protobuf version. You just have
to make
Yes, very early on during initialization of the library. My only concern
with upgrading to a new version of protobuf is backward compatibility.
Should I stick with 2.6 or go with 3.x? I know I can't use any of the new
features but will all my current messages be recognizable across the