bloritsch@dtri.net
==============
What steps will reproduce the problem?
1. Create a base type that is [ProtoContract]
2. Include 1 or more [ProtoInclude] statements
3. In one of the ProtoInclude types, mark an unsupported
property type as [ProtoMember]
4. Try to guess which type and which member is the culprit from the
exception message.
What is the expected output? What do you see instead?
The exception message should include the Type name and the Property/Field name
along with the message. Example: "InternalOption.Value: object is not a
supported type"
What version of the product are you using? On what operating system?
protobuf-net v2 r480
On Windows 7
Please provide any additional information below.
Good error messages really help speed up finding bad attributes.
Original issue reported on code.google.com by blorit...@gmail.com on 31 May 2012 at 5:59
Original issue reported on code.google.com by
blorit...@gmail.comon 31 May 2012 at 5:59