Author Topic: Syncronizing Code Files  (Read 4361 times)

snupea

  • EA Novice
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
Syncronizing Code Files
« on: June 08, 2005, 07:26:34 am »
We are using the Corporate Edition EA 5.0 connecting to SQL Server.  We have 5 developers using EA making changes to classes and coding classes.  We are having a problem when we reverse engineering code to sync up our class models.

Each of us have our folders set up differently and we are having a problem syncing them up after the first sync.  It seems like EA is storing the path somewhere and we can't seem to change it or remove it so other developers can sync the same class at a later date.

Has anyone had this problem or know how we can resolve it?

Thanks!
???

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8085
  • Karma: +118/-20
    • View Profile
Re: Syncronizing Code Files
« Reply #1 on: June 08, 2005, 03:15:55 pm »
EA has something to cater for exactly this situation.

Look at Configuration | Local Paths.

See http://sparxsystems.com.au/EAUserGuide/index.html?localpaths.htm for more details.

Simon

snupea

  • EA Novice
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
Re: Syncronizing Code Files
« Reply #2 on: June 09, 2005, 04:36:10 am »
We have looked at the local paths, however, I am not sure that meets our needs.  We are coding in C# and have many different namespaces.  Each namespace has a class model that will point to a different physical path on the developer's computer.  How will the different packages know what local path to use?

Thanks for any help you can give us!

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8085
  • Karma: +118/-20
    • View Profile
Re: Syncronizing Code Files
« Reply #3 on: June 21, 2005, 04:37:46 pm »
This situation is exactly what the local paths were created for.

Each class will have its its filename set to something like "%PATHNAME%\Package1\Package2\ClassName.cs".

Each computer is then set up with PATHNAME corresponding the the relevant directory for that computer.

I hope this helps.

Simon