Apoligies in advance. for my newbie question.
The Release Notes for the 4.1 SDK say -
Currently, USBizi (FEZ Mini, FEZ Domino, FEZ Rhino, FEZ Panda) does not support serialization.
this refers to -
[quote]Level interrupts are not supported in this release. Edge interrupts are supported.
XTEA encryption support : GHIElectronics.NETMF.System.XTEA
Dropped NETMF’s cryptography support.
Fixed: SPI baudrate settings.
I’m thinking about a lot of things… can some one clarify or give me an Idea of what this applies to.
Those are many notes about the SDK, serialization is not supported on USBizi and this has nothing to do with other items you listed from the release notes
I’ve found the XML classes in NETMF to be a ‘work in progress’. They tend eat up precious memory quickly and we’ve found a bug or two along the way. See [url]
http://www.tinyclr.com/forum/1/3488/[/url] for a bug example. That’s not to say you can’t crank out a class that will transform an object into xml. You can, it’s just not as easy as in the full framework.
Thanks Gus and EricH… Im just busy, busy, busy… Thanks for the tips, happy coding
@ EricH XML?! I think he is talking about serializing object, right?
@ Gus - sorry, must be I was still in day job mode. I do occasionally mix up which classes do what between frameworks and wonder why stuff doesn’t compile!
@ Alex - I have written NETMF that serves up XML over HTTP that can be deserialized by a client running the full framework, but that is obviously not the same thing under the hood :
Here’s a (somewhat dated) quote from Elze Kool’s blog on the topic:
XML serialization is not available on the Micro Framework and Binary serialization goes different then on the desktop and compact .NET versions.
How can I serialize then?
Through the Reflection class. This class is used to get information of classes and objects in C#. With .NET Micro Framework this class has two extra methods: Reflection.Serialize() and Reflection.Deserialize(). These methodes handle the serialization. The binary serialized byte array thats generated can be stored in a file, send trough a network, with RF, etc… One drawback is that its not compatible with the desktop and compact .NET versions of binary serialized objects.
Full article at
Thanks for the Info ErickH and Gus, I was wondering wich one (serialization); TTL, CMOS, XML, SOAP, ect… or just some. I want to place the small FEZmini in a compact environment, to up link data through Bluetooth, Xbee, Internet, or any other means; to a CPU, Smart Phone, and what not ( I know theres many protocols to do that)
Sorry for any confusion.
…EricH, your XML project looks very neat, theres many apps for that.