Check out this DMReview article.
Dr. Richard Gray and of his staff of six used PV-WAVE, a sophisticated visual analysis tool from Visual Numerics, to build a "first of its kind" research application for identifying fibrillation.
Dr. Richard Gray and of his staff of six used PV-WAVE, a sophisticated visual analysis tool from Visual Numerics, to build a "first of its kind" research application for identifying fibrillation.
ObjectOutputStream
and then calling writeObject(this)
. If you add implements Serializable
and add a couple UIDs, you're all set. Actually very easy.[Serializable()]
attribute set and you also implement ISerializable
. All fine so far, but implementing this interface means you need a GetObjectData
method too. Visual Studio drops the skeleton in your class, but that's were my general clue of what I was doing stopped.GetObjectData
to add whatever local variables you want to serialize. In this case, it was just that Hashtable, so my method looks like: public void GetObjectData(SerializationInfo info, StreamingContext context)
{
info.AddValue("hashSeries", hashSeries);
}
Deserialize
on the input stream and cast it back to your original object. This constructor needs the same parameters as that GetObjectData
method and basically just does things in reverse:protected StockDatabase(SerializationInfo info, StreamingContext context)
{
hashSeries = (Hashtable)info.GetValue("hashSeries", typeof(Hashtable));
}
Simple as pie right? I really didn't spin my wheels too long on this one, but I did do some real research trying to find a good example and piece together the bits from the various things I saw on the way to something that works. The best example ended up being the one for the Deserialize Method even though it doesn't serialize a class object.