Book a Demo

Author Topic: Version Control Configuration  (Read 5398 times)

armin

  • EA User
  • **
  • Posts: 63
  • Karma: +0/-0
  • mission possible
    • View Profile
Version Control Configuration
« on: December 22, 2006, 05:11:06 am »
Hello,

our EA-project contains a lot of version controlled packages . Whenever someone opens the project for the first time he will be prompted to configure the version control settings for his workstation.
As there is the same configuration on every workstation, I woluld like to know if there is another way to do the configuration than to click on every configuration and select the path?

Regards and Merry Christmas to all of you....

sbockheim

  • EA Novice
  • *
  • Posts: 18
  • Karma: +0/-0
    • View Profile
Re: Version Control Configuration
« Reply #1 on: December 22, 2006, 06:27:34 am »
I am looking to do the same thing. I am going to attempt this early next year. I will post my results here.
I asked the sparx team for some guidance and this was their response.  
-----

Whilst it is not possible to perform the task you describe from the command line, EA does have an API, that exposes many functions for working with your model.

Amongst the functions available through this interface are functions to enumerate the packages/elements in the model and functions to perform most of EA's version control operations.

Please see EA's Help documentation for further information.  

Below are links to the relevant pages in the online version of EA's help documentation.
http://sparxsystems.com.au/EAUserGuide/theautomationinterface.htm
http://sparxsystems.com.au/EAUserGuide/package_2.htm

The version control functions are described toward the bottom of the list of Package Methods.



charge

  • EA User
  • **
  • Posts: 22
  • Karma: +0/-0
    • View Profile
Re: Version Control Configuration
« Reply #2 on: January 23, 2007, 05:40:55 am »
I am trying to use the VersionControlCheckout method on the package, but I get this error: "Invalid rectangle (Exception from HRESULT: 0x8004000D (OLE_E_INVALIDRECT))"

Any Idee's?

armin

  • EA User
  • **
  • Posts: 63
  • Karma: +0/-0
  • mission possible
    • View Profile
Re: Version Control Configuration
« Reply #3 on: January 23, 2007, 06:21:45 am »
Hi,

which kind of version control you are using?

charge

  • EA User
  • **
  • Posts: 22
  • Karma: +0/-0
    • View Profile
Re: Version Control Configuration
« Reply #4 on: January 26, 2007, 02:08:14 am »
We use the apply/release User Lock functionality in the corporate version. I can't find a way to lock and edit element via the automation interface.... (only via the dirty way to edit the database directly)

michael.harding

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
  • EA User
    • View Profile
Re: Version Control Configuration
« Reply #5 on: February 20, 2007, 08:51:59 pm »
armin - I think what you're looking for is this registry key:
HKEY_CURRENT_USER\Software\Sparx Systems\EA400\EA\OPTIONS\VCConfigs

This appears to contain the Version Control configs. You could create a registry key and import it with the "regedit.exe /s file.reg" command.

armin

  • EA User
  • **
  • Posts: 63
  • Karma: +0/-0
  • mission possible
    • View Profile
Re: Version Control Configuration
« Reply #6 on: March 19, 2007, 03:32:04 am »
Hi Michael,

Thank you for your hint. I tested your proposal but there is another key in the registry you have to consider:
HKEY_USERS\S-1-5-21-1570180440-1338462480-2053579262-1005\Software\Sparx Systems\EA400\EA\OPTIONS\VCConfigs. The node "S-1-5-21-1570180440-1338462480-2053579262-1005" is client specific and must be replaced for a particular client. So I've found at least 4 places where EA looks for its SCC-Information:
1.)"path.txt" in EA bin directory
2.)"path.txt" in "%USERPROFILE%\Anwendungsdaten\Sparx Systems\EA"
3.)HKEY_USERS\S-1-5-21-1570180440-1338462480-2053579262-1005\Software\Sparx Systems\EA400\EA\OPTIONS\VCConfigs
4.) HKEY_CURRENT_USER\Software\Sparx Systems\EA400\EA\OPTIONS\VCConfigs

Only if you write the necessary information to all these locations you can hope that EA uses the right configuration. I think EA has to think about this behaviour

Regards Armin