bugDotGNU Portable.NET - Bugs: bug #16764, Binary Serialize doesn't work --...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #16764: Binary Serialize doesn't work -- reading or writing

Submitter:  David Logan <djlogan>
Submitted:  Tue 06 Jun 2006 06:18:07 PM UTC
   
 
Category:  None Severity:  3 - Normal
Item Group:  None Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open

Sun 04 May 2008 09:20:36 PM UTC, comment #3: 

http://groups.google.us/group/jou-tubex
Here You Will Find The Web's Best Ever Sex Blog With Loads Of Free Porn Videos Updated Daily.
http://groups.google.us/group/animalporn-tube
They actually look at different directories using the same path.
danwalsh.
http://groups.google.us/group/animal-sex-tubex
2007-12-03 12:14 am UTC (link) Track This
So user a looking at /tmp see's a different directory then user b looking at /tmp.

Anonymous
Wed 07 Jun 2006 01:57:24 AM UTC, comment #2: 

Basically, in ObjectManager.cs, we need to figure out how to call Apply(). This will call the constructor.

Possible ways to get to apply would be to call RegisterObject() with a containing ID, but I don't know yet how to accomplish that.

You could also call RecordFixup(). But I don't yet know how/when to call that one either.

Anonymous
Tue 06 Jun 2006 10:34:35 PM UTC, comment #1: 

The crash is because the namespace was different on M$ than it was on dotgnu. Change "namespace testserialization" to "namespace testserializer", and dotgnu no longer crashes. Now it just fails to deserialize correctly.

David Logan <djlogan>
Tue 06 Jun 2006 06:18:07 PM UTC, original submission:  

There are two similar issues:
1) Serializing a class, the subsequently deserializing a class, does not work. The deserialization fails to load the class correctly.

I think both the write AND the read are broken. The reason is issues #2:

2) Using M$ C# (DevStudio), running the same program, produces a serialize file that is four bytes greater than dotgnu. Both files are attached. Then, trying to get dotgnu to READ the M$ serialize file crashes.

====================================

So, I think the deserialize is functioning incorrectly. When that gets fixed, I think you will find that the serialize code is not properly writing the type to the serialize file. But I suppose we will find that out for sure when we get there.

Attached is: test.cs  - You can run the serialize/deserialize. Or, you can comment out/remove the serialize, and run only the deserialize using the M$ created serialize file.

testserialize.dat.created.by.xxx - the serialize files created by dotgnu and M$.

David Logan <djlogan>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attached Files
file #10134:  Class1.cs added by djlogan (2KiB - text/plain - My test.cs on Unix, it's the test app)
file #10133:  testserializer.dat.created.by.m$ added by djlogan (152B - application/octet-stream - testserializer.dat.created.by.m$)
file #10132:  testserializer.dat.created.by.dotgnu added by djlogan (148B - application/octet-stream - testserializer.dat.created.by.dotgnu)

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

 

Follow 3 latest changes.

Date Changed by Updated Field Previous Value => Replaced by
2006-06-06 djlogan Attached File- Added Class1.cs, #10134
2006-06-06 djlogan Attached File- Added testserializer.dat.created.by.m$, #10133
2006-06-06 djlogan Attached File- Added testserializer.dat.created.by.dotgnu, #10132

Back to the top

Powered by Savane 3.13-4448.
Corresponding source code