protobuf-net v2 alpha - problems with Dictionary<string,string>?

Posted by Steve on Stack Overflow See other posts from Stack Overflow or by Steve
Published on 2010-06-16T22:53:23Z Indexed on 2010/06/17 22:33 UTC
Read the original article Hit count: 327

Filed under:

protobuf-net

I was using a version of v2 of protobuf-net from a few weeks ago quite successfully. (I want to use V2 due to the speed of the pre-compiled serializer running on the Compact Framework.) Everything worked great until I tried to serialize an object with a property of type Dictionary. I received the following error:

{"No serializer defined for type: System.Collections.Generic.KeyValuePair`2[[System.String, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.String, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]]"}

It looked like there were recent changes made to improve Dictionary support, so I grabbed the latest code from today. After building the CF3.5 and FF3.5 dlls, I tried again. Now I get a different error "The model cannot be changed once frozen." If I remove the ProtoMember attribute from the Dictionary property all seems to work well.

Has anyone succcessfully used a Dictionary in v2 of protobuf-net? Is this still too early of a release to be using? My speed tests showed v2 being twice as fast, does that seem accurate (validating my desire to use the less stable v2 pre-alpha bits.)

Related posts about protobuf-net

protobuf-net - backticks, Dictionaries & .proto files

as seen on Stack Overflow - Search for 'Stack Overflow'
I'm trying to talk to a C# program that uses protobuf-net from an iphone using http://code.google.com/p/metasyntactic/wiki/ProtocolBuffers Unfortunately the .proto file I've been given (generated from the C# source code) includes an a line that protoc is rejecting: repeated Pair_Guid_List`1 Local… >>> More
protobuf-net: Issues deserializing DataMember fields in lieu of read-only property

as seen on Stack Overflow - Search for 'Stack Overflow'
I'm having issues deserializing certain properties of ORM-generated entities using protobuf-net. I suspect something in the way the ORM manages serialization attributes on read-only properties (uses public backing fields with DataMember attributes & [de]serializes) those instead of the corresponding… >>> More
How to choose between protobuf-csharp-port and protobuf-net

as seen on Stack Overflow - Search for 'Stack Overflow'
Hi Folks, I've recently had to look for a C# porting of the Protocole Buffer library originally developped by Google. And guess what, I found two projects owned both by two very well known persons here: protobuf-csharp-port, written by Jon Skeet and protobuf-net, written by Mark Gravell. My question… >>> More
protobuf-net: Incorrect wire-type deserializing TimeSpan

as seen on Stack Overflow - Search for 'Stack Overflow'
I get this exception when my client application is trying to deserialize a message comming from WCF service ("Incorrect wire-type deserializing TimeSpan"). I'm using .NET 3.5 SP1 and latest version of protobuf-net (1.0.0.275). I have no idea what could be the issue comming from. I don't undersand… >>> More
Deserializing a type at the current stream position with protobuf-net

as seen on Stack Overflow - Search for 'Stack Overflow'
I'm serializing several objects into a single stream, but when i try to read them back, i can't seem to get anything but the last object: ProtoBuf.Serializer.Serialize(stream, postA1); ProtoBuf.Serializer.Serialize(stream, postB2); stream.Position = 0; var postA2 = ProtoBuf.Serializer.Deserialize<Post>(stream); var… >>> More

Developer IT