c# - Serializing on Desktop, Deserializing in Silverlight -
I'm trying to create content through a small desktop app, and it should appear inside a silverlight application I am here. (I'm making a simple, simple C # object, and trying to keep it going smoothly.) Reference is a game of some kind, where I have a desktop tool that allows me to create and edit the content I want , And then Silverlight Bayreyers consume it.
How can I serial some (desktop) in C # and can it be serialized in serial lights? There is a small library created for my sermonization; It uses Silverlight, and a simple Is it possible to do this? I do not like to return the data to save the data manually as text and then parse it, and if possible I do not like to use an embedded database. I can have lists of lists and other complex data, and manually parsing it is very painful. If this is not possible, then what options do I have? Edit: Protoboot .net looks fine, but as I mentioned in Mark's comment, I use the serializer in my own library. I am here. This means that encryption will be broken to serialize them to add attribution to the user classes of my persistence. I do not want to do this. Break Encapsulation The goal of my library (continuous storage) is the user's game maker. They will use the library to continue the information within their game. Therefore, they only use PersistentStorage.dll. Internally, a serializer (currently, Mike Talbot for Silverlight and a simple binary for non-silverlight) uses continuous storage data to continue. For me, "O people, ask me to use my library I know that in the form of a work around, I can say to them everything with You You can try to serialize sections between .NET 4 and seriallight . You might want to use SilverlightSerializer to share the object between Silverlight and .NET 4, perhaps in a WCF link. The important thing to do in these situations is to define the sections that you want to share in the Silverlight Assembly which only systems, systems. Core and MSCLB are the requirements for those assemblies that can be used in both types of projects. If you define your classes in this way, they can be deserialized at back end without any problem, and reference anything and it does not work. Fortunately you will need the most of the assemblies of those systems! BinaryFormatter for each desktop, it's OK; But across the platform, these two are clearly inconsistent. [ProtoContract] or [serializable] breaks" encapsulation "on all your classes is. It means the user knows about the interior of my library use, that they should not. I can change the serials yesterday, and they should not care about them. [persistMe] and that the form of a plain blank feature In turn, which in turn enhances all the features of my serial needs, but I hope there will be no attribution required to use other serials like Mike Talbot.
Comments
Post a Comment