I have an application which worked fine under beta2 of the .NET framework, that uses SoapFormatter to store an object to a file.

On upgrading to the release version of .NET 2.0 I now find the behaviour of SoapFormatter has changed - it now serializes/deserializes the private members of inherited classes into the subclass entry.

This means that a large xml file saved under beta2 has 17 elements in one class, but now expects 23 elements to be deserialized using 2.0 - resulting in an exception and inability to load the file.

Q1. Is there a way to disable this behaviour to be able to load and convert this file?
   or
Q2. Is there a way to catch and ignore the exceptions on loading?

Howard