Simply put this is not possible. The GetHashCode function returns a signed integer which contains 2^32 possible unique values. On a 64 bit platform you can have many more than 2^32 different objects running around and hence they cannot all have unique hash codes.

The only way to approach this is to create a different hashing function which returns a type with the capacity greater than or equal to the number of values that could be created in the running system.

"Unique hash" is generally a contradiction in terms, even in general terms (and it s more obviously impossible if you re trying to use an Int32 as the hash value). From the wikipedia entry:

A hash function is any well-defined procedure or mathematical function that converts a large, possibly variable-sized amount of data into a small datum, usually a single integer that may serve as an index to an array. The values returned by a hash function are called hash values, hash codes, hash sums, or simply hashes.

Note the "small datum" bit - in other words, there will be more possible objects than there are possible hash values, so you can t possibly have uniqueness.

Now, it sounds like you actually want the hash to be a string... which means it won t be of a fixed size (but will have to be under 2GB or whatever the limit is). The simplest way of producing this "unique hash" would be to serialize the object and convert the result into a string, e.g. using Base64 if it s a binary serialization format, or just the text if it s a text-based one such as JSON. However, that s not what anyone else would really recognise as "hashing".

A unique hash code is impossible without constraints on your input space. This is because Object.GetHashCode is an int. If you have more than Int32.MaxValue objects then at least two of them must map to same hash code (by the pigeonhole principle).

Define a custom type with restrained input (i.e., the number of possible different objects up to equality is less than Int32.MaxValue) and then, and only then, is it possible to produce a unique hash code. That s not saying it will be easy, just possible.

Alternatively, don t use the Object.GetHashCode mechanism but instead some other way of representing hashes and you might be able to do what you want. We need clear details on what you want and are using it for to be able to help you here.

As others have stated, hash code will never be unique, that s not the point.

The point is to help your Dictionary<string, MyObject> foo to find the exact instance faster. It will use the hash code to narrow the search to a smaller set of objects, and then check them for equality.

You can use the Guid class to get unique strings, if what you need is a unique key. But that is not a hash code.