Saving Version Control xojo_project still produces unwanted changes

Thanks, Greg. I have this issue also, and appreciate the work.

A related issue is that backwards compatiblity has been fragile lately, e.g. Web2 Backwards Compatibility 2020R2 to earlier versions is fragile

Would it be possible for the IDE to have the concept of “aliases”?

Between 2020R1 and 2020R2, Web text fields had the property renamed from .Value to .Text. This change was migrated to the VCP format as well, which was a breaking change.

I think a better strategy would have been to not change the text project format, but simply have the IDE map the new/old property name upon loading/saving.

If you did this via lookups, it would then be pretty easy for future IDEs to keep a small table:

IDEVersion  PropertyName   NewIDEVersion NewPropertyName
2020R1     .Value           2020R2       .Text

which could be used on-the-fly for loading/saving.