Loss of object Info during serialization into sql server database in C# csharp .net

Is there a way to make the parent object know about the child's info? If not, then I guess I will return a serialized version of the data, as opposed to a parent object which is then serialized.

So is there a way for the parent object to know about the child's info, to make it persistant so that when serialization takes place it knows? I'm guessing not....

Actually, just test a basic set of inherited classes, and if you serialize an object which has been casted to its parent class, there shouldn't be an issue. Apologies for that, I was thinking about the XmlSerializer's behaviour. I've also realised it Serializes private members too.

Have you tried serializing & deserializing without the rounds trip to the database, and verifying that that works. That way you can confirm the database storage isn't the issue.

Also, are you implementing your own serialization in this class?

      System.IO.MemoryStream ms = new System.IO.MemoryStream();
      BinaryFormatter sz = new BinaryFormatter();
 
      cMasterTest testParameters = interfaceToUserControl.getTestParameters();
      sz.Serialize(ms, testParameters);
 
      ms.Position = 0;
      cMasterTest cmt = (cMasterTest)bf.Deserialize(ms);
                                              

1:
2:
3:
4:
5:
6:
7:
8:

I have successfully serialized to memory and de-serialized from memory without round trip to the database, so that works. In the code below you can see the test I ran.

Does this mean it is a database issue? I am using SQL Server 2005 Express. The name of the table is tblSerializedTests. The script that creates the table is in the code snippet.

The way I enter and retrieve the serialized info from the database, you can see that in my original posting above.

What other info can I give you or what's something else I can try?

One interesting note: When I serialize to the memory stream, it is of 724 length and 1024 capacity. But when I de-serialize, it is of length 725 and also 725 capacity. Not sure if that means anything, but I would expect the memory streams to be equal in length.

//*** SUGGESTED TEST (THIS WORKS) ***\\
MemoryStream ms2 = new MemoryStream();
BinaryFormatter bf2 = new BinaryFormatter();
bf2.Serialize(ms2, testParameters);
ms2.Position = 0;          
 
// Deserialize to parent
cMasterTest cmt = (cMasterTest)bf2.Deserialize(ms2);
 
 // Deserialize to child
 cHP3245A_testParam param = (cHP3245A_testParam)cmt; // Success!
// *** END OF SUGGESTED TEST ***\\
 
//*** DATABASE RELATED ***\\
-- Create test object table
CREATE TABLE tblSerializedTests
 (unique_id integer not null,
  test_name VARCHAR(25) not null,
  test_object VARBINARY(MAX) not null);
//*** END DATABASE RELATED ***\\

                                              

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:

The solution, it turns out, was quite simple. My SQL statement was not pulling the object I thought it was pulling from the database. The CLUE to this should have been the different in number of bytes going into the database then going out.

In any case, I resolved the SQL statement and it now works!!!

Thank you for leading me on the right path, I could not have done it without people like you.

The solution, it turns out, was quite simple. My SQL statement was not pulling the object I thought it was pulling from the database. The CLUE to this should have been the different in number of bytes going into the database then going out.

In any case, I resolved the SQL statement and it now works!!!

Thank you for leading me on the right path, I could not have done it without people like you.