# Version control compatibility of the Project object

**URL:** <https://forum.inductiveautomation.com/t/version-control-compatibility-of-the-project-object/4167>\
**Category:** Ignition\
**Created:** [March 19, 2012, 12:06pm UTC](https://forum.inductiveautomation.com/t/version-control-compatibility-of-the-project-object/4167 "2012-03-19T12:06:15Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![cgz](https://avatars.discourse-cdn.com/v4/letter/c/8dc957/32.png) [@cgz](https://forum.inductiveautomation.com/u/cgz)\
**Post date:** [March 19, 2012, 12:06pm UTC](https://forum.inductiveautomation.com/t/version-control-compatibility-of-the-project-object/4167/1 "2012-03-19T12:06:15Z")

</div>

I’d like to use the standard version control tools (SVN, Git, Mercurial etc.) for tracking  
the changes in an Ignition Project.

Is there anything regarding this on the drawing board?

I could imagine it could be something that “exploded” the contents of a .proj  
file into a set of directories and subdirectories, where a file would represent  
possibly a component.

Or at least so, that only actual binary data was gzip/base64 -encoded within  
a .proj file, but nothing else. All that could, would be clean XML and hence,  
providing easy diff comparison of versions. Also the composition should be  
stable, so that the internal order wouldn’t change between subsequent .proj exports.

Thanks!