I can\'t seem to get a handle on my list of sortables. They are a list of list elements, each with a
What\'s going on behind the scenes in .NET (de)serialization that makes it behave the way it does in the following scenario? (This is a test app that just illustrates my setup.)
I\'m trying out Generics and I had this (not so) great idea of creating an XMLSerializer class. The code I pieced together is below:
I\'m communicating with several services from a SL component using both TCP sockets & HTTP web requests and we are discussing what (data) format to use - JSON or XML.
I am running into this massive problem, I have to for various reasons change the Interface defintion to something different. This interface was serialised as a开发者_高级运维 blob into the database. N
I have these classes: [DataContract] public class ErrorBase {} [DataContract] public class FileMissingError: ErrorBase {}
I have a some large data structure (N > 10,000) that usually only needs to be created once (at runtime), and can be reused many times afterwards, but it needs to be loaded very quickly. (It is used fo
Closed. This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this
I have a base class in one assembly and a large number of generated classes in another that inherit from the base class. Using protobuf-net (r282) to serialize a list of the base type fails when attem
Is it possible to create an interface extending the Serializable interface? If yes, will that extended interface be开发者_如何学JAVAhave like the Serilizable interface? If not, why?Yes, you can exten
加载中,请稍侯......