The API documentation for the FileDescriptor.ReplaceReference Method says:
"The file being replaced and the replacement file must share ancestry (i.e. they must have the same InternalName). Documents have the same internal name if they are copied using 'Save Copy As' or a file explorer copy."
Why? That isn't required if you right click in the browser and choose "Replace Base Component". Also, the FileDescriptor.ReferenceInternalNameDifferent Property documentation says it "Gets whether the internal name of the referenced file is different from the last time the parent (referencing) file was saved." Obviously, the internal names being different was expected in some cases. It's unclear why this limitation on the ReplaceReference method exists.
Is there a workaround? Otherwise I'll have to go to the trouble of recreating all parts I want to switch from a copy of another one.
