Frameworks and Oxygen versions

[dcramer]

On the root element of a .framework file is a version number corresponding to the version of Oxygen that created/edited the file:

Code: Select all

<serialized version="18.1" xml:space="preserve">

	<serializableOrderedMap>

	...

We have users on more than one version of Oxygen, but for development it's convenient to use the latest. I notice that when I use 19.1 to edit a framework created with 18.1, Oxygen makes changes beyond what I intended to make. The changes are minor, but obviously 19.1 is upgrading the file to match what it expects. My concern is that if I distribute a framework created with 19.1 back to some users who are still on an earlier version, they users of the earlier version my encounter unexpected behavior. What's the best practice in this case?

David

[sorin_carbunaru]

Hello David,

The version from the root is there only for telling which oXygen version was used when the framework was last edited. It's not used for anything special. The content of the .framework file is what really matters.

The best practice would be to use the framework from the oldest version that the users have, as some framework customizations from the latest version may not be backward compatible.

Best regards,
Sorin Carbunaru
oXygen XML