Hi Ross,
Before version Q3 2010, RadFilter used the
ObjectStateFormatter for serialization and deserialization of filter expressions. The biggest caveat to this approach was that the ObjectStateFormatter did not support deserialization of object data serialized from another assembly version. Starting with Q3 2010, RadFilter now supports a second type of serialization - through the
BinaryFormatter. The BinaryFormatter has the
AssemblyFormat=FormatAssemblyStyle.Simple property set, meaning it can deserialize object data from a previous assembly version. Obviously, the BinaryFormatter provides greater flexibility, but comes at a cost too - it doesn't work in a medium trust environment.
Because the version of RadFilter (Q1 2010) you used when you serialized your settings data did not support the BinaryFormatter, you cannot deserialize this state with the latest version of the controls. The serialized data in your database is meaningful to the ObjectStateFormatter only, but the latter will fail to deserialize it with a version of RadControls different than the one you used when serializing.
Veli
the Telerik team