I serialize some configuration objects and store the result bytes within a database.

```
new BinaryFormatter().Serialize(memoryStream, instance);
Convert.ToBase64String(memoryStream.ToArray());

```

These objects will be deserialized later. 

```
new BinaryFormatter().Deserialize(memoryStream);

```

It's possible, that the Application has some new assembly versions at the time of deserialization. In general it works well, but sometimes I get a file load exception: 
*"The located assembly's manifest definition does not match the assembly reference."*. The assemblies work all with strong naming, can that be the problem and how could I avoid this problem?

Thanks for help