There are some examples of using an existing .proto file (generated from ProtoBuf.Serializer.GetProto ();) and De-serial in raw objects by a dynamic object or plain object
Let me emphasize that this is a problem, I am facing to improve the debugging tool for my memory cache - without the use of the objective app in human readable To be able to create an object (as I would store .proto for each type in the cache, because it was serialized, even then existed).
There are no performance considerations in this solution, all the options are in the table. I would be happy if such a protocol was a way of doing in the protocol, but if I need to use code generation / optional libraries , So this is fine. I do not know what the most prudent approach will be.
There is no one with ProtoFoolf-net .proto parsing tool, though Google-code download (but Nugget download) as well as one of the companion tools "Proton", which has some support for it. It can be referred to (this is just a pure assembly) and is used - it is exactly how the integration test operates for it. This tool works as a C # code generator; Hover to CSharpCodeProvider and you have a viable, if original, mechanism to process data in memory. You do not want to process such a large amount in a single app-domain, however - it is not good to unload runtime assemblies.
What would you like to do, it would be better to translate the specially designed tool for that scenario, translating it to "someone who wanted this scenario sufficiently that they were examined, It took time to design, implement, test and support. "
No comments:
Post a Comment