I am not sure that what I found is related but it confused me for several hours.I had a XMLPersistanceMapper saving my stuff , and I did not have any problems
I added a Image:Image attribute, and also added a button opening up a file dialog to assing a picture to the bytearray that the Image attribute was implemented as.
And then my app stopped working. I simply would not save any data at all to the xml file after I had assigned something to the byte array...
It turned out that there was an undocumented feature in the XMLPersistanceMapper that when working with relative paths like "./data.xml" it did Directory.GetCurrent() - and it did this for each save... So when I had found and assigned a picture I had also changed the result of Directory.GetCurrent()... Sneaky...
The XMLPersistanceMapper is updated in the later builds to use the Directory.GetCurrent() the first time only and then keep on to the result so that you keep saving to the same place you loaded from...