Hi All,

I've got a module I'm building with alot of different settings to it. Instead of creating a table with each setting in it's own column, I created a serializable object with the various setting properties in it.
Once the user has set all the settings, the module makes a binary image of the settings object then stores that binary in the database along with the moduleID to pull back later.
When the module needs the settings, it grabs the binary from the database, deserializes it, casts it as a settings object and all the settings are available.
This work VERY well, makes adding new settings a cinch.
Everything works perfectly on my development machine. I've installed the module on the production server and it also works perfectly
.....until I install an updated module package. i.e. version 1.0 of the module is installed on the production server, everything is ok. I can use the module as expected. But if I reinstall the module (same version, no changes, or new version with some changes) all existing modules of that type on the site stop working with the error "Unable to cast Modulesettings to Modulesettings".
I can add new instances of the module to the site and they all work fine, but pre-existing modules get that error.

Any ideas on what's going on?