When renaming a SymbolDefinition, it identifies LayerDefinition resources which contain references to these, but does not properly update the resources. See example LayerDefinition and SymbolDefinition in ticket #1170
This was due to the composite references that are constructed slightly different.
I changed the resource update system to use the xml documents in raw, rather than the .Net objects, as this makes it much easier to find the ResourceId's. It also has the benefit that the .Net serialization/deserialization won't accidentially remove fragments.
Fixed with r4430.
This was due to the composite references that are constructed slightly different. I changed the resource update system to use the xml documents in raw, rather than the .Net objects, as this makes it much easier to find the ResourceId's. It also has the benefit that the .Net serialization/deserialization won't accidentially remove fragments.