# duplicateReference Hashcode in Serializers

**URL:** <https://community.thinkgeo.com/t/duplicatereference-hashcode-in-serializers/2093>\
**Category:** WinForms\
**Created:** [September 13, 2012, 9:25am UTC](https://community.thinkgeo.com/t/duplicatereference-hashcode-in-serializers/2093 "2012-09-13T09:25:54Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![Damian1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@Damian1](https://community.thinkgeo.com/u/Damian1)\
**Post date:** [September 13, 2012, 9:25am UTC](https://community.thinkgeo.com/t/duplicatereference-hashcode-in-serializers/2093/1 "2012-09-13T09:25:54Z")

</div>

Hi,

Previously,&nbsp;I&nbsp;logged&nbsp;a&nbsp;post&nbsp;in&nbsp;where&nbsp;I&nbsp;found&nbsp;in&nbsp;a&nbsp;serialized&nbsp;data&nbsp;file&nbsp;a&nbsp;hash&nbsp;code&nbsp;for&nbsp;a&nbsp;duplicateReference&nbsp;that&nbsp;had&nbsp;been&nbsp;reused&nbsp;for&nbsp;elements&nbsp;in&nbsp;which&nbsp;it&nbsp;didn't&nbsp;apply.&nbsp;&nbsp;This&nbsp;post&nbsp;is&nbsp;called&nbsp;"Deserializing&nbsp;Error&nbsp;for&nbsp;Layer&nbsp;Overlay".&nbsp;&nbsp;We&nbsp;did&nbsp;not&nbsp;find&nbsp;a&nbsp;solution&nbsp;with&nbsp;our&nbsp;test&nbsp;project,&nbsp;but&nbsp;chocked&nbsp;it&nbsp;up&nbsp;to&nbsp;version&nbsp;of&nbsp;MapSuite.

Since&nbsp;then,&nbsp;I&nbsp;have&nbsp;continued&nbsp;to&nbsp;get&nbsp;similar&nbsp;errors,&nbsp;but&nbsp;not&nbsp;always&nbsp;for&nbsp;the&nbsp;same&nbsp;elements.&nbsp;&nbsp;I've&nbsp;seen&nbsp;instances&nbsp;where&nbsp;Fonts&nbsp;are&nbsp;being&nbsp;cross-referenced&nbsp;to&nbsp;featureSources,&nbsp;featureSources&nbsp;for&nbsp;featureSourceColumns&nbsp;and&nbsp;other&nbsp;similar&nbsp;unmatched&nbsp;types.

Essentially,&nbsp;the&nbsp;only&nbsp;thing&nbsp;that&nbsp;I&nbsp;can&nbsp;conclude&nbsp;is&nbsp;that&nbsp;there&nbsp;is&nbsp;an&nbsp;error&nbsp;somewhere&nbsp;in&nbsp;the&nbsp;code&nbsp;where&nbsp;the&nbsp;serializer&nbsp;writes&nbsp;data&nbsp;and&nbsp;decides&nbsp;to&nbsp;replace&nbsp;an&nbsp;element&nbsp;with&nbsp;a&nbsp;duplicateReference&nbsp;flag&nbsp;in&nbsp;order&nbsp;to&nbsp;save&nbsp;disk&nbsp;space&nbsp;with&nbsp;the&nbsp;output&nbsp;file.

Since&nbsp;this&nbsp;error&nbsp;seems&nbsp;to&nbsp;be&nbsp;a&nbsp;shot&nbsp;in&nbsp;the&nbsp;dark&nbsp;to&nbsp;find,&nbsp;can&nbsp;you&nbsp;please&nbsp;provide&nbsp;me&nbsp;with&nbsp;a&nbsp;solution&nbsp;in&nbsp;which&nbsp;the&nbsp;serializer&nbsp;will&nbsp;simply&nbsp;write&nbsp;the&nbsp;XML&nbsp;stream&nbsp;as&nbsp;is&nbsp;with&nbsp;no&nbsp;duplicateReference&nbsp;replacement&nbsp;flags?&nbsp;&nbsp;I&nbsp;do&nbsp;not&nbsp;currently&nbsp;see&nbsp;any&nbsp;options&nbsp;when&nbsp;calling&nbsp;the&nbsp;.Serialize&nbsp;method.

I&nbsp;am&nbsp;using&nbsp;version&nbsp;6.0.0.75&nbsp;in&nbsp;case&nbsp;this&nbsp;issue&nbsp;has&nbsp;been&nbsp;addressed&nbsp;since&nbsp;then.

Thanks,

Damian

---

<div class="post-metadata">

**Author:** ![Edgar](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/e/b487fb/32.png) [@Edgar](https://community.thinkgeo.com/u/Edgar)\
**Post date:** [September 13, 2012, 9:31pm UTC](https://community.thinkgeo.com/t/duplicatereference-hashcode-in-serializers/2093/2 "2012-09-13T21:31:26Z")

</div>

Hi&nbsp;Damian,&nbsp;  
&nbsp;&nbsp;  
&nbsp;I&nbsp;read&nbsp;the&nbsp;post&nbsp;“Deserializing&nbsp;Error&nbsp;for&nbsp;Layer&nbsp;Overlay”&nbsp;and&nbsp;it&nbsp;seems&nbsp;that&nbsp;you&nbsp;just&nbsp;provided&nbsp;the&nbsp;serialized&nbsp;xml&nbsp;file&nbsp;which&nbsp;already&nbsp;contains&nbsp;the&nbsp;error&nbsp;hashcode&nbsp;and&nbsp;we&nbsp;didn’t&nbsp;get&nbsp;the&nbsp;original&nbsp;one.&nbsp;could&nbsp;you&nbsp;please&nbsp;send&nbsp;a&nbsp;full&nbsp;sample&nbsp;to&nbsp;us&nbsp;to&nbsp;have&nbsp;a&nbsp;test?&nbsp;The&nbsp;requirements&nbsp;for&nbsp;the&nbsp;sample&nbsp;are:&nbsp;  
&nbsp;1),&nbsp;Runnable.&nbsp;  
&nbsp;2),&nbsp;Contains&nbsp;the&nbsp;original&nbsp;data,&nbsp;not&nbsp;the&nbsp;xml&nbsp;files,&nbsp;&nbsp;e.g.&nbsp;all&nbsp;the&nbsp;overlays&nbsp;you&nbsp;mentioned&nbsp;in&nbsp;that&nbsp;post.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Only&nbsp;in&nbsp;this&nbsp;way,&nbsp;we&nbsp;can&nbsp;work&nbsp;with&nbsp;the&nbsp;exactly&nbsp;same&nbsp;scenario&nbsp;as&nbsp;yours&nbsp;and&nbsp;recreate&nbsp;the&nbsp;issue.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Thanks&nbsp;in&nbsp;advance,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Edgar

---

<div class="post-metadata">

**Author:** ![Damian1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@Damian1](https://community.thinkgeo.com/u/Damian1)\
**Post date:** [September 21, 2012, 11:06am UTC](https://community.thinkgeo.com/t/duplicatereference-hashcode-in-serializers/2093/3 "2012-09-21T11:06:38Z")

</div>

Edgar,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Sorry&nbsp;for&nbsp;the&nbsp;delayed&nbsp;reply.&nbsp;I&nbsp;forgot&nbsp;to&nbsp;add&nbsp;myself&nbsp;to&nbsp;the&nbsp;topic&nbsp;notification.&nbsp;&nbsp;Wish&nbsp;this&nbsp;was&nbsp;a&nbsp;default&nbsp;when&nbsp;submitting&nbsp;a&nbsp;post.&nbsp;  
&nbsp;&nbsp;  
&nbsp;I’ve&nbsp;resent&nbsp;the&nbsp;data&nbsp;to&nbsp;support&nbsp;email&nbsp;as&nbsp;it’s&nbsp;too&nbsp;big&nbsp;to&nbsp;attach,&nbsp;but&nbsp;I&nbsp;do&nbsp;not&nbsp;want&nbsp;to&nbsp;go&nbsp;down&nbsp;this&nbsp;rabbit&nbsp;hole&nbsp;again.&nbsp;&nbsp;I&nbsp;have&nbsp;some&nbsp;people&nbsp;getting&nbsp;rather&nbsp;upset&nbsp;when&nbsp;their&nbsp;files&nbsp;refuse&nbsp;to&nbsp;load&nbsp;because&nbsp;they&nbsp;are&nbsp;being&nbsp;serialized&nbsp;incorrectly.&nbsp;  
&nbsp;&nbsp;  
&nbsp;There&nbsp;is&nbsp;no&nbsp;test&nbsp;project&nbsp;that&nbsp;replicates&nbsp;the&nbsp;issue,&nbsp;only&nbsp;my&nbsp;active&nbsp;distribution&nbsp;software&nbsp;which&nbsp;I&nbsp;will&nbsp;not&nbsp;be&nbsp;sending&nbsp;you.&nbsp;&nbsp;However,&nbsp;since&nbsp;there&nbsp;is&nbsp;nothing&nbsp;that&nbsp;I&nbsp;can&nbsp;do&nbsp;to&nbsp;interrupt&nbsp;the&nbsp;Serialize&nbsp;method,&nbsp;I&nbsp;really&nbsp;don’t&nbsp;see&nbsp;why&nbsp;there&nbsp;is&nbsp;a&nbsp;need&nbsp;for&nbsp;this.&nbsp;&nbsp;You&nbsp;really&nbsp;need&nbsp;to&nbsp;be&nbsp;checking&nbsp;into&nbsp;your&nbsp;code&nbsp;as&nbsp;to&nbsp;how&nbsp;duplicate&nbsp;references&nbsp;are&nbsp;assigned.&nbsp;  
&nbsp;&nbsp;  
&nbsp;My&nbsp;question&nbsp;is&nbsp;clear.&nbsp;&nbsp;Can&nbsp;I&nbsp;get&nbsp;a&nbsp;solution&nbsp;where&nbsp;I&nbsp;can&nbsp;force&nbsp;the&nbsp;serializer&nbsp;to&nbsp;stop&nbsp;substituting&nbsp;duplicate&nbsp;references&nbsp;when&nbsp;writing&nbsp;data?&nbsp;  
&nbsp;&nbsp;  
&nbsp;After&nbsp;I&nbsp;get&nbsp;to&nbsp;a&nbsp;point&nbsp;where&nbsp;I&nbsp;have&nbsp;files&nbsp;written&nbsp;out&nbsp;correctly&nbsp;and&nbsp;no&nbsp;more&nbsp;users&nbsp;screaming&nbsp;at&nbsp;me,&nbsp;I&nbsp;will&nbsp;be&nbsp;happy&nbsp;to&nbsp;spend&nbsp;more&nbsp;time&nbsp;investigating&nbsp;the&nbsp;duplicate&nbsp;references&nbsp;and&nbsp;will&nbsp;help&nbsp;as&nbsp;much&nbsp;as&nbsp;possible&nbsp;to&nbsp;provide&nbsp;you&nbsp;data&nbsp;and&nbsp;test&nbsp;projects&nbsp;to&nbsp;replicate&nbsp;the&nbsp;issue&nbsp;in&nbsp;your&nbsp;environment.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Regards,&nbsp;  
&nbsp;Damian

---

<div class="post-metadata">

**Author:** ![Edgar](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/e/b487fb/32.png) [@Edgar](https://community.thinkgeo.com/u/Edgar)\
**Post date:** [September 23, 2012, 10:41pm UTC](https://community.thinkgeo.com/t/duplicatereference-hashcode-in-serializers/2093/4 "2012-09-23T22:41:21Z")

</div>

Hi&nbsp;Damian,

I&nbsp;got&nbsp;your&nbsp;data&nbsp;and&nbsp;did&nbsp;the&nbsp;following&nbsp;test&nbsp;with&nbsp;6.0.0.75,

1),&nbsp;Change&nbsp;the&nbsp;hashCode&nbsp;at&nbsp;line&nbsp;320860&nbsp;and&nbsp;320876&nbsp;from&nbsp;22170731&nbsp;to&nbsp;22170732.

 ![](https://community.thinkgeo.com/uploads/default/original/2X/3/3ed5c8abb856624f2bd2c685315983de6dd94c52.PNG)

2),&nbsp;Run&nbsp;your&nbsp;sample&nbsp;and&nbsp;deserialize&nbsp;the&nbsp;modified&nbsp;file&nbsp;to&nbsp;an&nbsp;object,&nbsp;it&nbsp;works&nbsp;fine.

3),&nbsp;Serialize&nbsp;the&nbsp;object&nbsp;to&nbsp;a&nbsp;new&nbsp;file.

4),&nbsp;Rerun&nbsp;the&nbsp;sample&nbsp;and&nbsp;choose&nbsp;the&nbsp;new&nbsp;file&nbsp;to&nbsp;deserialize&nbsp;and&nbsp;display,&nbsp;it&nbsp;works&nbsp;fine.

&nbsp;

It&nbsp;runs&nbsp;without&nbsp;any&nbsp;exception,&nbsp;so&nbsp;I&nbsp;think&nbsp;our&nbsp;serializer&nbsp;has&nbsp;no&nbsp;problem,&nbsp;but&nbsp;the&nbsp;wrong&nbsp;hashCode&nbsp;in&nbsp;your&nbsp;data&nbsp;must&nbsp;be&nbsp;caused&nbsp;by&nbsp;some&nbsp;run&nbsp;time&nbsp;error&nbsp;etc.,&nbsp;is&nbsp;it&nbsp;possible&nbsp;for&nbsp;you&nbsp;to&nbsp;modify&nbsp;the&nbsp;wrong&nbsp;hasCode&nbsp;to&nbsp;a&nbsp;unique&nbsp;one&nbsp;e.g.&nbsp;22170732?

Hope&nbsp;it&nbsp;helps,

Edgar

---

<div class="post-metadata">

**Author:** ![Damian1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@Damian1](https://community.thinkgeo.com/u/Damian1)\
**Post date:** [September 25, 2012, 10:13am UTC](https://community.thinkgeo.com/t/duplicatereference-hashcode-in-serializers/2093/5 "2012-09-25T10:13:07Z")

</div>

Edgar,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Reassigning&nbsp;the&nbsp;hash&nbsp;code&nbsp;for&nbsp;the&nbsp;duplicate&nbsp;reference&nbsp;to&nbsp;a&nbsp;made&nbsp;up&nbsp;number&nbsp;which&nbsp;is&nbsp;not&nbsp;assigned&nbsp;elsewhere&nbsp;obviously&nbsp;removes&nbsp;the&nbsp;exception,&nbsp;but&nbsp;it&nbsp;doesn’t&nbsp;fix&nbsp;the&nbsp;problem&nbsp;for&nbsp;2&nbsp;reasons.&nbsp;  
&nbsp;&nbsp;  
&nbsp;1.&nbsp;&nbsp;I&nbsp;can’t&nbsp;detect&nbsp;if&nbsp;a&nbsp;hash&nbsp;code&nbsp;has&nbsp;been&nbsp;assigned&nbsp;incorrectly&nbsp;until&nbsp;the&nbsp;Serializer&nbsp;yields&nbsp;an&nbsp;exception.&nbsp;&nbsp;Not&nbsp;helpful&nbsp;as&nbsp;it&nbsp;just&nbsp;indicates&nbsp;a&nbsp;problem&nbsp;to&nbsp;the&nbsp;user&nbsp;which&nbsp;they&nbsp;don’t&nbsp;know&nbsp;how&nbsp;to&nbsp;fix.&nbsp;&nbsp;Further,&nbsp;it&nbsp;would&nbsp;be&nbsp;programmatically&nbsp;irritating&nbsp;to&nbsp;have&nbsp;to&nbsp;write&nbsp;some&nbsp;code&nbsp;to&nbsp;read&nbsp;the&nbsp;file&nbsp;and&nbsp;pair&nbsp;duplicates&nbsp;to&nbsp;their&nbsp;hash&nbsp;codes&nbsp;to&nbsp;test&nbsp;their&nbsp;type&nbsp;compatibility&nbsp;and&nbsp;then&nbsp;to&nbsp;further&nbsp;replace&nbsp;them&nbsp;with&nbsp;made&nbsp;up&nbsp;numbers.&nbsp;  
&nbsp;&nbsp;  
&nbsp;2.&nbsp;&nbsp;In&nbsp;this&nbsp;case,&nbsp;the&nbsp;duplicate&nbsp;reference&nbsp;is&nbsp;not&nbsp;replacing&nbsp;a&nbsp;lot&nbsp;of&nbsp;XML&nbsp;parameters&nbsp;since&nbsp;we’re&nbsp;talking&nbsp;about&nbsp;a&nbsp;column&nbsp;type&nbsp;that&nbsp;only&nbsp;has&nbsp;a&nbsp;name&nbsp;property.&nbsp;&nbsp;In&nbsp;some&nbsp;cases,&nbsp;the&nbsp;hash&nbsp;code&nbsp;is&nbsp;substituted&nbsp;for&nbsp;a&nbsp;completely&nbsp;different&nbsp;type&nbsp;which&nbsp;many&nbsp;parameters&nbsp;are&nbsp;required.&nbsp;&nbsp;For&nbsp;instance,&nbsp;I&nbsp;have&nbsp;seen&nbsp;a&nbsp;duplicate&nbsp;hash&nbsp;code&nbsp;used&nbsp;for&nbsp;a&nbsp;zoomLevelSet.&nbsp;&nbsp;When&nbsp;these&nbsp;parameters&nbsp;are&nbsp;not&nbsp;all&nbsp;defined,&nbsp;replacing&nbsp;the&nbsp;hash&nbsp;code&nbsp;with&nbsp;a&nbsp;made&nbsp;up&nbsp;number&nbsp;only&nbsp;means&nbsp;the&nbsp;object&nbsp;will&nbsp;not&nbsp;display&nbsp;properly.&nbsp;  
&nbsp;&nbsp;  
&nbsp;None&nbsp;of&nbsp;my&nbsp;code&nbsp;does&nbsp;anything&nbsp;or&nbsp;writes&nbsp;out&nbsp;anything&nbsp;to&nbsp;the&nbsp;Serialized&nbsp;file&nbsp;(or&nbsp;assigns&nbsp;hash&nbsp;codes),&nbsp;so&nbsp;how&nbsp;can&nbsp;this&nbsp;be&nbsp;something&nbsp;I’m&nbsp;doing&nbsp;in&nbsp;code?&nbsp;&nbsp;There&nbsp;are&nbsp;no&nbsp;runtime&nbsp;errors&nbsp;during&nbsp;the&nbsp;serialization&nbsp;of&nbsp;the&nbsp;files.&nbsp;If&nbsp;there&nbsp;were,&nbsp;then&nbsp;how&nbsp;could&nbsp;the&nbsp;serializer&nbsp;complete&nbsp;the&nbsp;closing&nbsp;XML&nbsp;statement?&nbsp;  
&nbsp;&nbsp;  
&nbsp;So,&nbsp;back&nbsp;to&nbsp;my&nbsp;question.&nbsp;&nbsp;Can&nbsp;I&nbsp;have&nbsp;a&nbsp;solution&nbsp;where&nbsp;the&nbsp;Serializer&nbsp;does&nbsp;not&nbsp;assign&nbsp;duplicate&nbsp;hash&nbsp;codes?&nbsp;&nbsp;I&nbsp;would&nbsp;also&nbsp;kindly&nbsp;request&nbsp;that&nbsp;you&nbsp;look&nbsp;at&nbsp;how&nbsp;hash&nbsp;codes&nbsp;are&nbsp;reused&nbsp;when&nbsp;serializing&nbsp;to&nbsp;see&nbsp;if&nbsp;there&nbsp;aren’t&nbsp;any&nbsp;obvious&nbsp;problems.&nbsp;&nbsp;We’re&nbsp;looking&nbsp;for&nbsp;a&nbsp;limit&nbsp;error&nbsp;here&nbsp;as&nbsp;it&nbsp;doesn’t&nbsp;manifest&nbsp;until&nbsp;the&nbsp;files&nbsp;contain&nbsp;1000’s&nbsp;of&nbsp;objects.&nbsp;&nbsp;Maybe,&nbsp;if&nbsp;you&nbsp;are&nbsp;writing&nbsp;data&nbsp;in&nbsp;chunks,&nbsp;some&nbsp;variable&nbsp;is&nbsp;getting&nbsp;reinitialized&nbsp;for&nbsp;each&nbsp;chunk&nbsp;instead&nbsp;of&nbsp;applying&nbsp;for&nbsp;the&nbsp;whole&nbsp;process.&nbsp;  
&nbsp;&nbsp;  
&nbsp;In&nbsp;the&nbsp;meantime,&nbsp;I&nbsp;will&nbsp;document&nbsp;the&nbsp;errors&nbsp;that&nbsp;I&nbsp;see&nbsp;and&nbsp;provide&nbsp;this&nbsp;to&nbsp;help&nbsp;better&nbsp;define&nbsp;the&nbsp;problem.&nbsp;  
&nbsp;&nbsp;  
&nbsp;I&nbsp;really&nbsp;do&nbsp;need&nbsp;a&nbsp;solution&nbsp;for&nbsp;this&nbsp;issue.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Damian

---

<div class="post-metadata">

**Author:** ![Damian1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@Damian1](https://community.thinkgeo.com/u/Damian1)\
**Post date:** [September 25, 2012, 2:53pm UTC](https://community.thinkgeo.com/t/duplicatereference-hashcode-in-serializers/2093/6 "2012-09-25T14:53:19Z")

</div>

Edgar,

I've&nbsp;found&nbsp;another&nbsp;example&nbsp;for&nbsp;you,&nbsp;this&nbsp;time&nbsp;with&nbsp;Zoom&nbsp;Level&nbsp;Sets.

Attached&nbsp;is&nbsp;a&nbsp;new&nbsp;GeoSerializerTester&nbsp;program&nbsp;as&nbsp;I've&nbsp;since&nbsp;updated&nbsp;my&nbsp;code&nbsp;to&nbsp;work&nbsp;in&nbsp;UTM's&nbsp;and&nbsp;display&nbsp;in&nbsp;Spherical&nbsp;Mercator.&nbsp;&nbsp;Also&nbsp;attached&nbsp;is&nbsp;a&nbsp;zip&nbsp;file&nbsp;with&nbsp;two&nbsp;text&nbsp;files&nbsp;that&nbsp;can&nbsp;be&nbsp;loaded&nbsp;into&nbsp;the&nbsp;GeoSerializerTester&nbsp;program.

When&nbsp;you&nbsp;load&nbsp;the&nbsp;first&nbsp;file,&nbsp;ZoomLevelHashCode.txt,&nbsp;you&nbsp;will&nbsp;see&nbsp;two&nbsp;points,&nbsp;but&nbsp;if&nbsp;you&nbsp;look&nbsp;at&nbsp;the&nbsp;file,&nbsp;there&nbsp;is&nbsp;actually&nbsp;a&nbsp;line&nbsp;and&nbsp;2&nbsp;points&nbsp;which&nbsp;should&nbsp;be&nbsp;displayed.

If&nbsp;you&nbsp;load&nbsp;the&nbsp;second&nbsp;file,&nbsp;ZoomLevelHashCodeFix.txt,&nbsp;you&nbsp;will&nbsp;see&nbsp;the&nbsp;1&nbsp;line,&nbsp;but&nbsp;only&nbsp;1&nbsp;of&nbsp;the&nbsp;2&nbsp;points.

The&nbsp;problem&nbsp;is&nbsp;because&nbsp;Hash&nbsp;Code&nbsp;64792811&nbsp;is&nbsp;assigned&nbsp;at&nbsp;zoomLevel03&nbsp;of&nbsp;the&nbsp;line&nbsp;object,&nbsp;but&nbsp;for&nbsp;some&nbsp;reason,&nbsp;that&nbsp;zoomLevel&nbsp;has&nbsp;been&nbsp;incorrectly&nbsp;written&nbsp;out&nbsp;as&nbsp;a&nbsp;defaultPointStyle&nbsp;even&nbsp;though&nbsp;the&nbsp;object&nbsp;is&nbsp;a&nbsp;line.&nbsp;&nbsp;The&nbsp;Hash&nbsp;Code&nbsp;is&nbsp;later&nbsp;used&nbsp;to&nbsp;reference&nbsp;zoomLevel01&nbsp;of&nbsp;one&nbsp;of&nbsp;the&nbsp;point&nbsp;type&nbsp;objects.&nbsp;&nbsp;Hence,&nbsp;that&nbsp;point&nbsp;displays&nbsp;when&nbsp;viewing&nbsp;the&nbsp;first&nbsp;file.

In&nbsp;the&nbsp;second&nbsp;file,&nbsp;I&nbsp;remove&nbsp;the&nbsp;erroneous&nbsp;reference&nbsp;to&nbsp;the&nbsp;defaultPointStyle&nbsp;in&nbsp;the&nbsp;line's&nbsp;zoom&nbsp;level&nbsp;set&nbsp;and&nbsp;hence&nbsp;the&nbsp;line&nbsp;displays&nbsp;correctly,&nbsp;but&nbsp;now&nbsp;not&nbsp;the&nbsp;point.&nbsp;&nbsp;The&nbsp;only&nbsp;way&nbsp;to&nbsp;fix&nbsp;this&nbsp;and&nbsp;display&nbsp;all&nbsp;3&nbsp;objects&nbsp;would&nbsp;be&nbsp;to&nbsp;copy&nbsp;the&nbsp;defaultPointStyle&nbsp;code&nbsp;down&nbsp;to&nbsp;the&nbsp;point&nbsp;object&nbsp;and&nbsp;remove&nbsp;the&nbsp;hash&nbsp;codes.

So,&nbsp;the&nbsp;question&nbsp;is&nbsp;how&nbsp;did&nbsp;a&nbsp;point&nbsp;style&nbsp;get&nbsp;assigned&nbsp;within&nbsp;a&nbsp;line&nbsp;styles&nbsp;zoom&nbsp;level&nbsp;set?&nbsp;&nbsp;The&nbsp;answer&nbsp;can&nbsp;not&nbsp;be&nbsp;anywhere&nbsp;but&nbsp;in&nbsp;the&nbsp;process&nbsp;where&nbsp;duplicateReference&nbsp;is&nbsp;assigned.&nbsp;

In&nbsp;this&nbsp;case,&nbsp;we're&nbsp;just&nbsp;lucky&nbsp;that&nbsp;this&nbsp;didn't&nbsp;throw&nbsp;an&nbsp;exception&nbsp;in&nbsp;the&nbsp;serializer&nbsp;since&nbsp;an&nbsp;object&nbsp;can&nbsp;always&nbsp;have&nbsp;default&nbsp;zoom&nbsp;level&nbsp;sets&nbsp;for&nbsp;points,&nbsp;lines&nbsp;and&nbsp;area&nbsp;types&nbsp;regardless&nbsp;of&nbsp;their&nbsp;well&nbsp;known&nbsp;type.&nbsp;

Further,&nbsp;this&nbsp;is&nbsp;only&nbsp;1&nbsp;case&nbsp;of&nbsp;about&nbsp;20&nbsp;similar&nbsp;cases&nbsp;all&nbsp;within&nbsp;the&nbsp;same&nbsp;originating&nbsp;file.&nbsp;&nbsp;Basically,&nbsp;I&nbsp;boiled&nbsp;the&nbsp;attached&nbsp;files&nbsp;down&nbsp;to&nbsp;a&nbsp;mimumum&nbsp;to&nbsp;clarify&nbsp;the&nbsp;problem.

I&nbsp;hope&nbsp;this&nbsp;is&nbsp;some&nbsp;help&nbsp;to&nbsp;prove&nbsp;that&nbsp;something&nbsp;quite&nbsp;bad&nbsp;is&nbsp;happening&nbsp;when&nbsp;duplicateReferences&nbsp;are&nbsp;being&nbsp;assigned&nbsp;in&nbsp;the&nbsp;Serializer.

-Damian

[ZoomLevelHashCodeExamples.zip](https://community.thinkgeo.com/uploads/default/original/2X/a/a439536e01afe2c75677e65368aa63c517e3c0be.zip) (6.86 KB)  
[GeoSerializerTester.zip](https://community.thinkgeo.com/uploads/default/original/2X/f/fd443ca64bd2226b0c50741f13f93f43f3bdae67.zip) (50.6 KB)

---

<div class="post-metadata">

**Author:** ![Edgar](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/e/b487fb/32.png) [@Edgar](https://community.thinkgeo.com/u/Edgar)\
**Post date:** [September 26, 2012, 3:26am UTC](https://community.thinkgeo.com/t/duplicatereference-hashcode-in-serializers/2093/7 "2012-09-26T03:26:39Z")

</div>

Damian,

Sorry&nbsp;for&nbsp;confusing&nbsp;you,&nbsp;I&nbsp;didn't&nbsp;mean&nbsp;you&nbsp;did&nbsp;something&nbsp;in&nbsp;your&nbsp;code,&nbsp;but&nbsp;the&nbsp;hash&nbsp;code&nbsp;is&nbsp;unstable&nbsp;sometimes.&nbsp;I&nbsp;serached&nbsp;the&nbsp;MSDN&nbsp;and&nbsp;knew&nbsp;that&nbsp;.NET&nbsp;Frameworkd&nbsp;does&nbsp;not&nbsp;guarantee&nbsp;the&nbsp;hash&nbsp;code&nbsp;is&nbsp;unique,&nbsp;orz.,&nbsp;we&nbsp;used&nbsp;to&nbsp;test&nbsp;it&nbsp;with&nbsp;the&nbsp;WorldMapkit&nbsp;which&nbsp;has&nbsp;thousands&nbsp;of&nbsp;layers&nbsp;and&nbsp;it&nbsp;works&nbsp;fine.&nbsp;Nevertheless&nbsp;we'll&nbsp;look&nbsp;for&nbsp;a&nbsp;solution&nbsp;to&nbsp;solve&nbsp;this.&nbsp;BTW,&nbsp;can&nbsp;you&nbsp;recreate&nbsp;the&nbsp;issue&nbsp;with&nbsp;the&nbsp;zoomlevel&nbsp;every&nbsp;time?&nbsp;If&nbsp;so,&nbsp;is&nbsp;it&nbsp;possible&nbsp;for&nbsp;you&nbsp;to&nbsp;provide&nbsp;the&nbsp;sample&nbsp;for&nbsp;us&nbsp;to&nbsp;have&nbsp;a&nbsp;test?&nbsp;We&nbsp;will&nbsp;appreciate&nbsp;that&nbsp;if&nbsp;you&nbsp;do&nbsp;so.

As&nbsp;the&nbsp;hash&nbsp;code&nbsp;is&nbsp;not&nbsp;unique,&nbsp;but&nbsp;it&nbsp;will&nbsp;still&nbsp;available&nbsp;for&nbsp;the&nbsp;following&nbsp;two&nbsp;scenarios:

1),&nbsp;Handling&nbsp;the&nbsp;repeat&nbsp;reference:&nbsp;FeatureLayer&nbsp;has&nbsp;a&nbsp;field&nbsp;"editTools"which&nbsp;type&nbsp;is&nbsp;EditTool,&nbsp;and&nbsp;a&nbsp;field&nbsp;"featureSource"&nbsp;which&nbsp;type&nbsp;is&nbsp;FeatureSource.&nbsp;and&nbsp;the&nbsp;EditTools&nbsp;has&nbsp;a&nbsp;field&nbsp;"featureSource"&nbsp;which&nbsp;is&nbsp;the&nbsp;same&nbsp;as&nbsp;FeatureLayer.FeatureSource,&nbsp;when&nbsp;serializing&nbsp;FeatureLayer,&nbsp;the&nbsp;FeatureSource&nbsp;will&nbsp;be&nbsp;serialized&nbsp;3&nbsp;times&nbsp;cause&nbsp;the&nbsp;FeatureLayer.FeatureSource,&nbsp;QueryTools.FeatureSource,&nbsp;EditTools.FeatureSource,&nbsp;so&nbsp;we&nbsp;are&nbsp;using&nbsp;the&nbsp;hash&nbsp;code&nbsp;to&nbsp;infer&nbsp;that&nbsp;the&nbsp;FeatureSource&nbsp;has&nbsp;already&nbsp;been&nbsp;serialized&nbsp;and&nbsp;tell&nbsp;the&nbsp;program&nbsp;not&nbsp;to&nbsp;serialize&nbsp;it&nbsp;again,&nbsp;this&nbsp;is&nbsp;used&nbsp;for&nbsp;making&nbsp;the&nbsp;result&nbsp;file's&nbsp;size&nbsp;smaller.

2),&nbsp;Handling&nbsp;the&nbsp;circular&nbsp;reference:&nbsp;assume&nbsp;there&nbsp;are&nbsp;two&nbsp;classes,&nbsp;class&nbsp;A&nbsp;{&nbsp;publc&nbsp;B&nbsp;b;&nbsp;},&nbsp;class&nbsp;B&nbsp;{&nbsp;public&nbsp;A&nbsp;a;&nbsp;},&nbsp;if&nbsp;we&nbsp;don't&nbsp;use&nbsp;the&nbsp;hash&nbsp;code&nbsp;two&nbsp;specify&nbsp;the&nbsp;serialized&nbsp;objects,&nbsp;this&nbsp;serialization&nbsp;will&nbsp;be&nbsp;endless,&nbsp;but&nbsp;by&nbsp;the&nbsp;hash&nbsp;code&nbsp;we&nbsp;can&nbsp;clearly&nbsp;know&nbsp;what&nbsp;object&nbsp;has&nbsp;been&nbsp;serialized,&nbsp;for&nbsp;this&nbsp;case&nbsp;

A&nbsp;a&nbsp;=&nbsp;new&nbsp;A();

a.b&nbsp;=&nbsp;new&nbsp;B();

a.b.a&nbsp;=&nbsp;a;

the&nbsp;xml&nbsp;will&nbsp;be&nbsp;

`<A type="A" hashCode="25560520" circularReference="parentNode" duplicateReference="true">  <b>    <a type="A" circularReference="childNode" hashCode="25560520" duplicateReference="true" />  </b></A>`

&nbsp;

Once&nbsp;we&nbsp;fixed&nbsp;this&nbsp;issue,&nbsp;we'll&nbsp;let&nbsp;you&nbsp;know.

Sorry&nbsp;for&nbsp;the&nbsp;inconvenience,

Edgar

---

<div class="post-metadata">

**Author:** ![Damian1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@Damian1](https://community.thinkgeo.com/u/Damian1)\
**Post date:** [September 27, 2012, 9:20am UTC](https://community.thinkgeo.com/t/duplicatereference-hashcode-in-serializers/2093/8 "2012-09-27T09:20:03Z")

</div>

Hi&nbsp;Edgar,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Thanks&nbsp;for&nbsp;looking&nbsp;into&nbsp;this.&nbsp;&nbsp;I&nbsp;really&nbsp;appreciate&nbsp;it.&nbsp;  
&nbsp;&nbsp;  
&nbsp;I&nbsp;will&nbsp;attempt&nbsp;to&nbsp;modify&nbsp;the&nbsp;test&nbsp;project&nbsp;to&nbsp;output&nbsp;the&nbsp;zoomLevel&nbsp;results&nbsp;consistently.&nbsp;&nbsp;I’ll&nbsp;send&nbsp;that&nbsp;early&nbsp;next&nbsp;week&nbsp;if&nbsp;I&nbsp;am&nbsp;successful.&nbsp;&nbsp;I&nbsp;have&nbsp;the&nbsp;feeling&nbsp;that&nbsp;it&nbsp;will&nbsp;produce&nbsp;them,&nbsp;but&nbsp;it&nbsp;won’t&nbsp;be&nbsp;the&nbsp;same&nbsp;effected&nbsp;element(s)&nbsp;each&nbsp;time.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Regards,&nbsp;  
&nbsp;Damian

---

<div class="post-metadata">

**Author:** ![Gary2](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/g/49beb7/32.png) [@Gary2](https://community.thinkgeo.com/u/Gary2)\
**Post date:** [September 27, 2012, 3:04pm UTC](https://community.thinkgeo.com/t/duplicatereference-hashcode-in-serializers/2093/9 "2012-09-27T15:04:24Z")

</div>

Hello&nbsp;Damian,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Ok,&nbsp;feel&nbsp;free&nbsp;to&nbsp;let&nbsp;us&nbsp;know&nbsp;your&nbsp;further&nbsp;information.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Regards,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Gary

---

<div class="post-metadata">

**Author:** ![Damian1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@Damian1](https://community.thinkgeo.com/u/Damian1)\
**Post date:** [October 4, 2012, 1:39pm UTC](https://community.thinkgeo.com/t/duplicatereference-hashcode-in-serializers/2093/10 "2012-10-04T13:39:56Z")

</div>

Gary/Edgar,

I&nbsp;have&nbsp;a&nbsp;test&nbsp;project&nbsp;that&nbsp;recreates&nbsp;the&nbsp;issue&nbsp;fairly&nbsp;regularly.&nbsp;&nbsp;I&nbsp;am&nbsp;sending&nbsp;it&nbsp;to&nbsp;[support@thinkgeo.com](mailto:support@thinkgeo.com)&nbsp;with&nbsp;subject&nbsp;of&nbsp;this&nbsp;topic.

The&nbsp;project&nbsp;has&nbsp;2&nbsp;shape&nbsp;file&nbsp;overlays&nbsp;and&nbsp;a&nbsp;point&nbsp;type&nbsp;overlay&nbsp;and&nbsp;a&nbsp;line&nbsp;type&nbsp;overlay.&nbsp;&nbsp;It&nbsp;also&nbsp;has&nbsp;two&nbsp;list&nbsp;boxes&nbsp;to&nbsp;display&nbsp;data&nbsp;about&nbsp;the&nbsp;lines&nbsp;and&nbsp;points.&nbsp;&nbsp;The&nbsp;serializer&nbsp;stores&nbsp;all&nbsp;these&nbsp;data&nbsp;and&nbsp;reads&nbsp;it&nbsp;back&nbsp;accordingly.

There&nbsp;are&nbsp;4&nbsp;buttons.

1.&nbsp;&nbsp;Save

2.&nbsp;&nbsp;Load

3.&nbsp;&nbsp;Add&nbsp;Lines

4.&nbsp;&nbsp;Add&nbsp;Points

If&nbsp;you&nbsp;use&nbsp;Load&nbsp;right&nbsp;now,&nbsp;it&nbsp;will&nbsp;pick-up&nbsp;the&nbsp;current&nbsp;SaveFile.txt&nbsp;in&nbsp;the&nbsp;Debug&nbsp;folder&nbsp;and&nbsp;you&nbsp;will&nbsp;see&nbsp;the&nbsp;most&nbsp;recent&nbsp;hash&nbsp;code&nbsp;error.

Now&nbsp;to&nbsp;replicate&nbsp;the&nbsp;issue&nbsp;for&nbsp;yourself,&nbsp;start&nbsp;anew&nbsp;by&nbsp;restarting&nbsp;the&nbsp;program.&nbsp;&nbsp;When&nbsp;it&nbsp;finishes&nbsp;loading,&nbsp;you&nbsp;can&nbsp;use&nbsp;Add&nbsp;Lines/Points&nbsp;and&nbsp;just&nbsp;start&nbsp;creating&nbsp;obects&nbsp;on&nbsp;the&nbsp;screen.&nbsp;&nbsp;I&nbsp;use&nbsp;the&nbsp;track&nbsp;overlay&nbsp;and&nbsp;then&nbsp;to&nbsp;speed&nbsp;things&nbsp;up&nbsp;write&nbsp;out&nbsp;400&nbsp;new&nbsp;feature&nbsp;layers&nbsp;starting&nbsp;with&nbsp;the&nbsp;base&nbsp;feature&nbsp;all&nbsp;separated&nbsp;by&nbsp;500m&nbsp;in&nbsp;the&nbsp;x&nbsp;direction.&nbsp;&nbsp;When&nbsp;you&nbsp;get&nbsp;to&nbsp;around&nbsp;4000&nbsp;lines&nbsp;and&nbsp;points,&nbsp;click&nbsp;the&nbsp;save&nbsp;button.&nbsp;&nbsp;This&nbsp;will&nbsp;write&nbsp;out&nbsp;to&nbsp;a&nbsp;SaveFile.txt&nbsp;in&nbsp;the&nbsp;Debug&nbsp;directory&nbsp;and&nbsp;then&nbsp;clear&nbsp;the&nbsp;current&nbsp;overlays.&nbsp;&nbsp;An&nbsp;example&nbsp;of&nbsp;what&nbsp;this&nbsp;should&nbsp;look&nbsp;like&nbsp;is&nbsp;in&nbsp;the&nbsp;attached&nbsp;image.

Now,&nbsp;click&nbsp;Load.&nbsp;&nbsp;If&nbsp;there&nbsp;was&nbsp;a&nbsp;hash&nbsp;code&nbsp;problem,&nbsp;you&nbsp;will&nbsp;see&nbsp;an&nbsp;error&nbsp;message.

For&nbsp;me,&nbsp;I&nbsp;started&nbsp;getting&nbsp;errors&nbsp;regularly&nbsp;with&nbsp;around&nbsp;3600&nbsp;elements.&nbsp;&nbsp;I&nbsp;do&nbsp;not&nbsp;know&nbsp;if&nbsp;this&nbsp;is&nbsp;CPU&nbsp;related,&nbsp;but&nbsp;I'm&nbsp;using&nbsp;x86&nbsp;in&nbsp;Debug&nbsp;mode.&nbsp;&nbsp;You&nbsp;may&nbsp;have&nbsp;to&nbsp;add&nbsp;more&nbsp;(or&nbsp;fewer)&nbsp;objects&nbsp;to&nbsp;see&nbsp;errors&nbsp;appear.

One&nbsp;thing&nbsp;that&nbsp;was&nbsp;clear&nbsp;when&nbsp;building&nbsp;this&nbsp;project&nbsp;was&nbsp;that&nbsp;you&nbsp;don't&nbsp;have&nbsp;a&nbsp;high&nbsp;likelihood&nbsp;of&nbsp;getting&nbsp;Exception&nbsp;errors&nbsp;using&nbsp;the&nbsp;Deserialize&nbsp;method&nbsp;just&nbsp;by&nbsp;serializing&nbsp;overlays.&nbsp;&nbsp;It's&nbsp;when&nbsp;I&nbsp;added&nbsp;in&nbsp;the&nbsp;two&nbsp;list&nbsp;boxes&nbsp;and&nbsp;started&nbsp;capturing&nbsp;more&nbsp;data&nbsp;of&nbsp;different&nbsp;types&nbsp;in&nbsp;the&nbsp;serialized&nbsp;file&nbsp;that&nbsp;the&nbsp;frequency&nbsp;increased.&nbsp;&nbsp;Consecuently,&nbsp;the&nbsp;bigger&nbsp;the&nbsp;file&nbsp;the&nbsp;more&nbsp;likeliness&nbsp;of&nbsp;an&nbsp;error.&nbsp;&nbsp;In&nbsp;my&nbsp;program,&nbsp;I&nbsp;have&nbsp;a&nbsp;similar&nbsp;structure,&nbsp;but&nbsp;with&nbsp;more&nbsp;overlays&nbsp;and&nbsp;more&nbsp;tables,&nbsp;so&nbsp;I&nbsp;get&nbsp;even&nbsp;more&nbsp;errors.&nbsp;&nbsp;Two&nbsp;were&nbsp;reported&nbsp;this&nbsp;morning&nbsp;alone&nbsp;from&nbsp;users&nbsp;and&nbsp;I&nbsp;had&nbsp;to&nbsp;"fix"&nbsp;their&nbsp;files&nbsp;by&nbsp;assigning&nbsp;the&nbsp;offending&nbsp;hash&nbsp;codes&nbsp;to&nbsp;unique&nbsp;values.

If&nbsp;you&nbsp;look&nbsp;in&nbsp;the&nbsp;Debug&nbsp;folder&nbsp;you&nbsp;will&nbsp;see&nbsp;two&nbsp;other&nbsp;SaveFiles&nbsp;which&nbsp;are&nbsp;other&nbsp;examples&nbsp;of&nbsp;serialized&nbsp;files&nbsp;with&nbsp;hash&nbsp;code&nbsp;errors&nbsp;using&nbsp;the&nbsp;same&nbsp;test&nbsp;program.&nbsp;&nbsp;All&nbsp;these&nbsp;files&nbsp;generated&nbsp;in&nbsp;the&nbsp;last&nbsp;hour,&nbsp;so&nbsp;it&nbsp;shouldn't&nbsp;be&nbsp;hard&nbsp;for&nbsp;you&nbsp;to&nbsp;validate&nbsp;on&nbsp;your&nbsp;side.

Please&nbsp;help&nbsp;me&nbsp;to&nbsp;find&nbsp;a&nbsp;solution&nbsp;as&nbsp;fast&nbsp;as&nbsp;possible.

Regards,

Damian

&nbsp;

---

<div class="post-metadata">

**Author:** ![Edgar](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/e/b487fb/32.png) [@Edgar](https://community.thinkgeo.com/u/Edgar)\
**Post date:** [October 8, 2012, 4:26am UTC](https://community.thinkgeo.com/t/duplicatereference-hashcode-in-serializers/2093/11 "2012-10-08T04:26:45Z")

</div>

Damian,&nbsp;  
&nbsp;&nbsp;  
&nbsp;We&nbsp;changed&nbsp;the&nbsp;hashcode&nbsp;to&nbsp;Guid&nbsp;to&nbsp;specify&nbsp;the&nbsp;different&nbsp;object,&nbsp;now&nbsp;I&nbsp;think&nbsp;your&nbsp;problem&nbsp;would&nbsp;be&nbsp;solved,&nbsp;please&nbsp;reserialize&nbsp;the&nbsp;objects&nbsp;using&nbsp;6.0.148.0&nbsp;or&nbsp;6.0.0.148&nbsp;dlls.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Hope&nbsp;it&nbsp;helps,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Edgar

---

<div class="post-metadata">

**Author:** ![Damian1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@Damian1](https://community.thinkgeo.com/u/Damian1)\
**Post date:** [October 8, 2012, 6:51pm UTC](https://community.thinkgeo.com/t/duplicatereference-hashcode-in-serializers/2093/12 "2012-10-08T18:51:23Z")

</div>

Hi&nbsp;Edgar,

I&nbsp;loaded&nbsp;the&nbsp;new&nbsp;library&nbsp;from&nbsp;production&nbsp;and&nbsp;I&nbsp;got&nbsp;a&nbsp;FormatException&nbsp;error&nbsp;running&nbsp;my&nbsp;sample&nbsp;and&nbsp;trying&nbsp;to&nbsp;save&nbsp;the&nbsp;file.

Here's&nbsp;the&nbsp;stack&nbsp;trace.

"&nbsp;&nbsp;&nbsp;at&nbsp;System.Number.StringToNumber(String&nbsp;str,&nbsp;NumberStyles&nbsp;options,&nbsp;NumberBuffer&&nbsp;number,&nbsp;NumberFormatInfo&nbsp;info,&nbsp;Boolean&nbsp;parseDecimal)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;System.Number.ParseInt32(String&nbsp;s,&nbsp;NumberStyles&nbsp;style,&nbsp;NumberFormatInfo&nbsp;info)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;System.Convert.ToInt32(String&nbsp;value)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.pCs=(Object&nbsp;pSs=,&nbsp;GeoObjectNode&nbsp;pis=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.jCs=(Object&nbsp;jSs=,&nbsp;GeoObjectNode&nbsp;jis=,&nbsp;String&nbsp;jys=,&nbsp;Type&nbsp;kCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.sys=(IEnumerable&nbsp;tCs=,&nbsp;GeoObjectNode&nbsp;tSs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.jCs=(Object&nbsp;jSs=,&nbsp;GeoObjectNode&nbsp;jis=,&nbsp;String&nbsp;jys=,&nbsp;Type&nbsp;kCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.CreateMemberNodeCore(String&nbsp;memberName,&nbsp;Object&nbsp;memberValue,&nbsp;Type&nbsp;memberType,&nbsp;Object&nbsp;memberOwner,&nbsp;GeoObjectNode&nbsp;baseMemberNode)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.CreateMemberNode(String&nbsp;memberName,&nbsp;Object&nbsp;memberValue,&nbsp;Type&nbsp;memberType,&nbsp;Object&nbsp;memberOwner,&nbsp;GeoObjectNode&nbsp;baseMemberNode)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.vSs=(Object&nbsp;vis=,&nbsp;GeoObjectNode&nbsp;vys=,&nbsp;FieldInfo&nbsp;wCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.tis=(Object&nbsp;tys=,&nbsp;GeoObjectNode&nbsp;uCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.jCs=(Object&nbsp;jSs=,&nbsp;GeoObjectNode&nbsp;jis=,&nbsp;String&nbsp;jys=,&nbsp;Type&nbsp;kCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.CreateMemberNodeCore(String&nbsp;memberName,&nbsp;Object&nbsp;memberValue,&nbsp;Type&nbsp;memberType,&nbsp;Object&nbsp;memberOwner,&nbsp;GeoObjectNode&nbsp;baseMemberNode)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.CreateMemberNode(String&nbsp;memberName,&nbsp;Object&nbsp;memberValue,&nbsp;Type&nbsp;memberType,&nbsp;Object&nbsp;memberOwner,&nbsp;GeoObjectNode&nbsp;baseMemberNode)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.vSs=(Object&nbsp;vis=,&nbsp;GeoObjectNode&nbsp;vys=,&nbsp;FieldInfo&nbsp;wCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.tis=(Object&nbsp;tys=,&nbsp;GeoObjectNode&nbsp;uCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.jCs=(Object&nbsp;jSs=,&nbsp;GeoObjectNode&nbsp;jis=,&nbsp;String&nbsp;jys=,&nbsp;Type&nbsp;kCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.sys=(IEnumerable&nbsp;tCs=,&nbsp;GeoObjectNode&nbsp;tSs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.jCs=(Object&nbsp;jSs=,&nbsp;GeoObjectNode&nbsp;jis=,&nbsp;String&nbsp;jys=,&nbsp;Type&nbsp;kCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.CreateMemberNodeCore(String&nbsp;memberName,&nbsp;Object&nbsp;memberValue,&nbsp;Type&nbsp;memberType,&nbsp;Object&nbsp;memberOwner,&nbsp;GeoObjectNode&nbsp;baseMemberNode)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.CreateMemberNode(String&nbsp;memberName,&nbsp;Object&nbsp;memberValue,&nbsp;Type&nbsp;memberType,&nbsp;Object&nbsp;memberOwner,&nbsp;GeoObjectNode&nbsp;baseMemberNode)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.vSs=(Object&nbsp;vis=,&nbsp;GeoObjectNode&nbsp;vys=,&nbsp;FieldInfo&nbsp;wCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.tis=(Object&nbsp;tys=,&nbsp;GeoObjectNode&nbsp;uCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.jCs=(Object&nbsp;jSs=,&nbsp;GeoObjectNode&nbsp;jis=,&nbsp;String&nbsp;jys=,&nbsp;Type&nbsp;kCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.CreateMemberNodeCore(String&nbsp;memberName,&nbsp;Object&nbsp;memberValue,&nbsp;Type&nbsp;memberType,&nbsp;Object&nbsp;memberOwner,&nbsp;GeoObjectNode&nbsp;baseMemberNode)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.CreateMemberNode(String&nbsp;memberName,&nbsp;Object&nbsp;memberValue,&nbsp;Type&nbsp;memberType,&nbsp;Object&nbsp;memberOwner,&nbsp;GeoObjectNode&nbsp;baseMemberNode)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.vSs=(Object&nbsp;vis=,&nbsp;GeoObjectNode&nbsp;vys=,&nbsp;FieldInfo&nbsp;wCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.tis=(Object&nbsp;tys=,&nbsp;GeoObjectNode&nbsp;uCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.jCs=(Object&nbsp;jSs=,&nbsp;GeoObjectNode&nbsp;jis=,&nbsp;String&nbsp;jys=,&nbsp;Type&nbsp;kCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.CreateMemberNodeCore(String&nbsp;memberName,&nbsp;Object&nbsp;memberValue,&nbsp;Type&nbsp;memberType,&nbsp;Object&nbsp;memberOwner,&nbsp;GeoObjectNode&nbsp;baseMemberNode)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.CreateMemberNode(String&nbsp;memberName,&nbsp;Object&nbsp;memberValue,&nbsp;Type&nbsp;memberType,&nbsp;Object&nbsp;memberOwner,&nbsp;GeoObjectNode&nbsp;baseMemberNode)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.vSs=(Object&nbsp;vis=,&nbsp;GeoObjectNode&nbsp;vys=,&nbsp;FieldInfo&nbsp;wCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.tis=(Object&nbsp;tys=,&nbsp;GeoObjectNode&nbsp;uCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.jCs=(Object&nbsp;jSs=,&nbsp;GeoObjectNode&nbsp;jis=,&nbsp;String&nbsp;jys=,&nbsp;Type&nbsp;kCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.CreateMemberNodeCore(String&nbsp;memberName,&nbsp;Object&nbsp;memberValue,&nbsp;Type&nbsp;memberType,&nbsp;Object&nbsp;memberOwner,&nbsp;GeoObjectNode&nbsp;baseMemberNode)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.CreateMemberNode(String&nbsp;memberName,&nbsp;Object&nbsp;memberValue,&nbsp;Type&nbsp;memberType,&nbsp;Object&nbsp;memberOwner,&nbsp;GeoObjectNode&nbsp;baseMemberNode)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.vSs=(Object&nbsp;vis=,&nbsp;GeoObjectNode&nbsp;vys=,&nbsp;FieldInfo&nbsp;wCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.tis=(Object&nbsp;tys=,&nbsp;GeoObjectNode&nbsp;uCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.jCs=(Object&nbsp;jSs=,&nbsp;GeoObjectNode&nbsp;jis=,&nbsp;String&nbsp;jys=,&nbsp;Type&nbsp;kCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.sys=(IEnumerable&nbsp;tCs=,&nbsp;GeoObjectNode&nbsp;tSs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.jCs=(Object&nbsp;jSs=,&nbsp;GeoObjectNode&nbsp;jis=,&nbsp;String&nbsp;jys=,&nbsp;Type&nbsp;kCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.CreateMemberNodeCore(String&nbsp;memberName,&nbsp;Object&nbsp;memberValue,&nbsp;Type&nbsp;memberType,&nbsp;Object&nbsp;memberOwner,&nbsp;GeoObjectNode&nbsp;baseMemberNode)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.CreateMemberNode(String&nbsp;memberName,&nbsp;Object&nbsp;memberValue,&nbsp;Type&nbsp;memberType,&nbsp;Object&nbsp;memberOwner,&nbsp;GeoObjectNode&nbsp;baseMemberNode)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.vSs=(Object&nbsp;vis=,&nbsp;GeoObjectNode&nbsp;vys=,&nbsp;FieldInfo&nbsp;wCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.tis=(Object&nbsp;tys=,&nbsp;GeoObjectNode&nbsp;uCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.jCs=(Object&nbsp;jSs=,&nbsp;GeoObjectNode&nbsp;jis=,&nbsp;String&nbsp;jys=,&nbsp;Type&nbsp;kCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.sys=(IEnumerable&nbsp;tCs=,&nbsp;GeoObjectNode&nbsp;tSs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.jCs=(Object&nbsp;jSs=,&nbsp;GeoObjectNode&nbsp;jis=,&nbsp;String&nbsp;jys=,&nbsp;Type&nbsp;kCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.CreateMemberNodeCore(String&nbsp;memberName,&nbsp;Object&nbsp;memberValue,&nbsp;Type&nbsp;memberType,&nbsp;Object&nbsp;memberOwner,&nbsp;GeoObjectNode&nbsp;baseMemberNode)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.CreateMemberNode(String&nbsp;memberName,&nbsp;Object&nbsp;memberValue,&nbsp;Type&nbsp;memberType,&nbsp;Object&nbsp;memberOwner,&nbsp;GeoObjectNode&nbsp;baseMemberNode)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.vSs=(Object&nbsp;vis=,&nbsp;GeoObjectNode&nbsp;vys=,&nbsp;FieldInfo&nbsp;wCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.tis=(Object&nbsp;tys=,&nbsp;GeoObjectNode&nbsp;uCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.jCs=(Object&nbsp;jSs=,&nbsp;GeoObjectNode&nbsp;jis=,&nbsp;String&nbsp;jys=,&nbsp;Type&nbsp;kCs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.iCs=(Object&nbsp;iSs=)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoObjectModeler.CreateModel(Object&nbsp;objectToModel,&nbsp;GeoObjectModelerMemberTypes&nbsp;memberTypes,&nbsp;BindingFlags&nbsp;bindingFlags,&nbsp;GeoObjectModelerDefaultValueMode&nbsp;defaultValueMode)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;ThinkGeo.MapSuite.Core.GeoSerializer.Serialize(Object&nbsp;objectToSerialize,&nbsp;Stream&nbsp;targetStream)\r\n&nbsp;&nbsp;&nbsp;at&nbsp;GeoSerializerTest.SerializationFunctions.WriteSerializedOverlays(FileStream&nbsp;output,&nbsp;Collection`1&nbsp;overlays,&nbsp;List`1&nbsp;textValues,&nbsp;Collection`1&nbsp;pointValues,&nbsp;Collection`1&nbsp;lineValues)&nbsp;in&nbsp;C:\\Users\\dhite\\Documents\\Visual&nbsp;Studio&nbsp;2010\\Projects\\GeoSerializerDuplicateHashCodeTester\\GeoSerializerTest\\SerializationFunctions.cs:line&nbsp;61"

&nbsp;

-Damian

---

<div class="post-metadata">

**Author:** ![Edgar](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/e/b487fb/32.png) [@Edgar](https://community.thinkgeo.com/u/Edgar)\
**Post date:** [October 8, 2012, 8:57pm UTC](https://community.thinkgeo.com/t/duplicatereference-hashcode-in-serializers/2093/13 "2012-10-08T20:57:53Z")

</div>

Oh,&nbsp;the&nbsp;circular&nbsp;reference&nbsp;was&nbsp;missed,&nbsp;now&nbsp;it&nbsp;has&nbsp;been&nbsp;fixed,&nbsp;please&nbsp;get&nbsp;6.0.149.0&nbsp;or&nbsp;6.0.0.149&nbsp;and&nbsp;have&nbsp;a&nbsp;try.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Sorry&nbsp;for&nbsp;the&nbsp;inconvenience,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Edgar

---

<div class="post-metadata">

**Author:** ![Damian1](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/d/5f9b8f/32.png) [@Damian1](https://community.thinkgeo.com/u/Damian1)\
**Post date:** [October 9, 2012, 10:06am UTC](https://community.thinkgeo.com/t/duplicatereference-hashcode-in-serializers/2093/14 "2012-10-09T10:06:47Z")

</div>

Hi&nbsp;Edgar,&nbsp;  
&nbsp;&nbsp;  
&nbsp;I’ve&nbsp;got&nbsp;the&nbsp;new&nbsp;version&nbsp;and&nbsp;tried&nbsp;it&nbsp;in&nbsp;my&nbsp;test&nbsp;project&nbsp;on&nbsp;roughly&nbsp;double&nbsp;the&nbsp;number&nbsp;of&nbsp;objects&nbsp;I&nbsp;expect&nbsp;in&nbsp;a&nbsp;normal&nbsp;project&nbsp;file&nbsp;and&nbsp;it’s&nbsp;working&nbsp;fine.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Sorry,&nbsp;I&nbsp;know&nbsp;you&nbsp;guys&nbsp;probably&nbsp;didn’t&nbsp;want&nbsp;to&nbsp;use&nbsp;GUID,&nbsp;but&nbsp;I&nbsp;really&nbsp;needed&nbsp;it&nbsp;for&nbsp;what&nbsp;we&nbsp;are&nbsp;doing.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Thanks&nbsp;again,&nbsp;  
&nbsp;Damian

---

<div class="post-metadata">

**Author:** ![Edgar](https://community.thinkgeo.com/letter_avatar_proxy/v4/letter/e/b487fb/32.png) [@Edgar](https://community.thinkgeo.com/u/Edgar)\
**Post date:** [October 9, 2012, 8:29pm UTC](https://community.thinkgeo.com/t/duplicatereference-hashcode-in-serializers/2093/15 "2012-10-09T20:29:17Z")

</div>

Damian,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Glad&nbsp;to&nbsp;hear&nbsp;that&nbsp;your&nbsp;project&nbsp;in&nbsp;working&nbsp;with&nbsp;the&nbsp;new&nbsp;version,&nbsp;and&nbsp;you’re&nbsp;right,&nbsp;the&nbsp;GUID&nbsp;is&nbsp;not&nbsp;the&nbsp;best&nbsp;solution&nbsp;cause&nbsp;the&nbsp;performance&nbsp;would&nbsp;be&nbsp;bad&nbsp;which&nbsp;is&nbsp;caused&nbsp;by&nbsp;generating&nbsp;the&nbsp;GUID&nbsp;if&nbsp;the&nbsp;objects&nbsp;count&nbsp;is&nbsp;very&nbsp;big,&nbsp;we’ll&nbsp;consider&nbsp;finding&nbsp;a&nbsp;better&nbsp;way&nbsp;to&nbsp;do&nbsp;it&nbsp;in&nbsp;the&nbsp;future.&nbsp;  
&nbsp;&nbsp;  
&nbsp;Regards,&nbsp;  
&nbsp;&nbsp;  
&nbsp;Edgar
