[Mono-bugs] [Bug 321322] Serialization formatters don't throw on missing fields

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=321322

https://bugzilla.novell.com/show_bug.cgi?id=321322#c2


Andrés G. Aragoneses <knocte at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |DUPLICATE

--- Comment #2 from Andrés G. Aragoneses <knocte at gmail.com> 2010-09-08 17:06:19 UTC ---
(In reply to comment #1)
> (In reply to comment #0)
> > ---- Additional Comments From robertj at gmx.net 2007-08-25 05:39:25 MST ----
> > 
> > Another closely related bug: When a field has been removed from
> > a class, the deserializer will throw an exception when it
> > tries to deserialize historical data.
> > 
> > MS.NET (both profiles) accepts this data.

Forgot this bit, which seems incorrect: Testing with latest MS.NET profiles
tells me that .NET 1.x throws but not the next versions. And Mono as of today
throws always, so this bug report is actually wrong (I thought it wasn't
because I thought it had to do with the field being *initialized* with data, as
opposed to an empty field).


> I've marked the bug as a dependency of the bug MONO81465 (bug 324144) but it

So, after a quick chat with Robert on IRC, we have determined that MS.NET never
throws in the latest .NET versions, and that comment from 2007-08-25 05:39:25
MST is actually stating the issue which is a duplicate of 324144 and the
opposite of this bug. For the sake of not over-complicating things, I'm going
to mark this bug as a dupe of that one, which has a more clear description
although it's not older.

*** This bug has been marked as a duplicate of bug 324144 *** http://bugzilla.novell.com/show_bug.cgi?id=324144

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.