Serialization load/save getting a different HashCode....

[Guilherme Morais]

Hi there... I´m facing a strange problem... I made a WebApp which serializate a complex object and save in the bank and load to save time of processor. When the WebApp save and read the object everything goes fine, but If I install one second WebApp in other server the same object is readed but the HashCode is differently from the original... Anyone has a opnion about that?? Thanks in advance...

[Natza Mitzi]

This is strange. You should try to compare and see if they are the same (time stamps and everything) If you can not find anything override the default Objectt.GetHashcode function and write your own. If you have an id for the object just use return id.GetHashCode(); in the override.

Natza Mitzi

[Wendelius]

I suppose this is normal behaviour. There are no guarantees that the hash code is the same when retrieved for an object nor that it is unique. If you want to predict the value of the hashcode (for example that it stays the same), you must build your own implementation. From BOL: The default implementation of the GetHashCode method does not guarantee unique return values for different objects. Furthermore, the .NET Framework does not guarantee the default implementation of the GetHashCode method, and the value it returns will be the same between different versions of the .NET Framework. Consequently, the default implementation of this method must not be used as a unique object identifier for hashing purposes.

[leppie]

You need to override GetHashCode() and provide your own consistent behaviour.

xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 4a out now (29 May 2008)

[leppie]

Natza Mitzi wrote:

This is strange.

It is not strange, it's perfect normal behaviour. I suggest you read about the topic a bit more. It has 'bitten' me a few times :)

xacc.ide - now with TabsToSpaces support
IronScheme - 1.0 alpha 4a out now (29 May 2008)

[Natza Mitzi]

You are correct. :~

Natza Mitzi