Convert object to byte array and viceversa (serialization)

mstampar (Miroslav Stampar) — Tue, 24 Apr 2007 22:48:07 GMT





// Convert an object to a byte array

private byte[] ObjectToByteArray(Object obj)

{

    if(obj == null)

        return null;

    BinaryFormatter bf = new BinaryFormatter();

    MemoryStream ms = new MemoryStream();

    bf.Serialize(ms, obj);

    return ms.ToArray();

}

// Convert a byte array to an Object

private Object ByteArrayToObject(byte[] arrBytes)

{

    MemoryStream memStream = new MemoryStream();

    BinaryFormatter binForm = new BinaryFormatter();

    memStream.Write(arrBytes, 0, arrBytes.Length);

    memStream.Seek(0, SeekOrigin.Begin);

    Object obj = (Object) binForm.Deserialize(memStream);

    return obj;

}

 

p.s. for custom classes add [Serializable] attribute to enable serialization

C# - XML serialization from string

hjnntaao (hjnntaao) — Wed, 06 Sep 2006 00:18:56 GMT

From http://weblogs.asp.net/whaggard/archive/2006/09/04/String-Streams-in-.Net.aspx



xmlSerializer.Deserialize(new StringReader(xmlString));

All Exceptions Created Equal

CloCkWeRX (Daniel O'Connor) — Fri, 17 Feb 2006 10:01:44 GMT

All exceptions are created equal. But what if you have a very good and pressing reason to serialize one to save it in a database? For instance, you had a collection of checks you wanted to run against some data, and save the results?

Ah, that's easy! serialize() was made for that! So off you trot, you make a few changes to the code, add a blank line here, a blank line there, and suddenly your code can't find the exact matches of the serialized object in the database.

HUH? What's going on? You're the exact same Exception I just threw three minutes ago, and you've sporadically broken?

It took me a while to twig. When you create an exception ($e = new Exception("foo");), it's shiny and new and listens when you do equality comparisions (==).

But things go awry: you throw a new Exception from your filter, catch it, and serialize it. You haven't remembered that...



$a = new Exception("foo");

try {

    throw $a; //Line 1

} catch (Exception $e) {

    throw $a; //Line 10;

}

will result in two difference traces. One saying "I was thrown on on line 1", the other "I was thrown on on line 10"...

Fuck oath, hello stupid coder. You've been wracking your brains wondering why every time you go off and edit a different bit of code it serializes differently; and there you have it.

How the hell do I fix it? Going to __sleep() on the job actually helps.



class DumbException extends Exception {

    /**

     * Cleanup anything we need before serialisation

     *

     * @return  string[]    An array of member varible names to serialize

     * @see     http://php.planetmirror.com/manual/en/language.oop5.magic.php

     */

    public function __sleep() {

        return array('string','code');

    }



    /**

     * Compare against another DumbException for equality.

     *

     * Since two exceptions can be !== because the trace / line / file

     * information is different, we need to do this.

     */

    public function cmp(DumbException $e) {

        return (serialize($e) == serialize($this));

    }

}



print '';

$a = new DumbException();

$b = new DumbException();





try {

    try {

        throw $b;

    } catch (Exception $e) {

        throw $a;

    }

} catch (Exception $e) {



    var_dump($a === $b);

    var_dump($a == $b);

    var_dump($b === $e);

    var_dump($b == $e);

    var_dump($a === $e);

    var_dump($a == $e);



    var_dump($b->cmp($e));

    var_dump($a->cmp($e));

}

print '';

?>

DZone Snippets: serialization code

Convert object to byte array and viceversa (serialization)

C# - XML serialization from string

All Exceptions Created Equal