Hermann.Gruber
Reputation: 1484
protobuf-net: properties versus fields
In our project, we have a data transfer object (DTO) class which is decorated with a [ProtoContract] attribute, and all of its members are public properties decorated with [ProtoMember] attributes - except that one of the members is a public field (by accident). Now we want to change the one public field into a property. Can this have an impact about the implicit protobuf contract? (We want to avoid breaking changes, and I suppose that this change is non-breaking, but I want to be sure.)
Upvotes: 3
Views: 509
Answers (1)
Marc Gravell
Reputation: 1062975
Yes, that's absolutely fine; protobuf-net won't care, and the serialized payload will remain identical.
Upvotes: 1
Related Questions
- Protobuf.net - all fields of a class required to be serialized
- Why does protobuf-net calls the getter of a property during deserialization but setter was not called yet
- Protobuf-net fails to serialize property with only getter - Cannot apply changes to property
- ProtoBuf.NET - Choose fields you want to load at runtime
- Protobuf-net appears to box value types. Is that actually so?
- protobuf-net not serializing C# properties with private setters
- Serializing complex properties without using Attributes
- protobuf-net serialization without attributes
- protobuf-net and an empty property in subclass
- Protobuf-net - Serialize only a few properties