Book a Demo

Author Topic: best practice for versioning .eap using EA integrated version control  (Read 4951 times)

danillodomingos

  • EA Novice
  • *
  • Posts: 11
  • Karma: +0/-1
    • View Profile
when using EA (version 9) integrated version control, only the packages xml are versioned in repository. This means that to version the entire project, we must check in all the packages in the project. The .eap file itself isnt versioned.

In this way, what is the best practice to work with the .eap? Is it good practice to maintain it in a central file system, where all the users can access it through the network, and work in the same file, checking in/out the packages they want to modify?

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile

Helmut Ortmann

  • EA User
  • **
  • Posts: 970
  • Karma: +42/-1
    • View Profile
Re: best practice for versioning .eap using EA integrated version control
« Reply #2 on: August 24, 2016, 02:27:34 pm »
Hi,

in my opinion the easiest way is to use up a database like SQL Server, My SQL or so. It's easy to setup, reliable and fast.

There are other good solutions like Version Control or Cloud.

Have also look in qwerties link. There you can read of a lot of experiences from very experienced persons.

Helmut
Coaching, Training, Workshop (Addins: hoTools, Search&Replace, LineStyle)