Frequently Asked Questions
Q | I want to use ASCET-SCMon the road – in a mobile use case. How do I proceed? |
A | See Online versus Offline Mode and Editing Items in Offline Mode. |
Q | I have to import an item by using File > Import in the ASCET component manager, but a different version of this item is already contained in the Subversion repository. How do I handle this item in ASCET-SCM? |
A | |
Q | Is checking out in ASCET-SCM the same as checking out in TortoiseSVN? |
A | No; unlike TortoiseSVN, the Checkout command in ASCET-SCM does not automatically read a complete repository to a new folder, but shows the complete repository content in the Checkout dialog box. There, you can select the item(s) you want to check out. See also Checking Out in ASCET-SCM versus Checking Out in TortoiseSVN. |
Q | I want to add new configurations to version control. Should I simply add the entire folder in which these configurations are contained? |
A | You are recommended to use Add and Commit New Configuration for an individual configuration (see Creating a Configuration), but not for a folder. If you apply this command at a folder level, each item within this folder will receive its own configuration. See also Managing ASCET Folders. |
Q | What happens when I unlock an item or configuration? |
A | Once you have unlocked an item or configuration, it is available for locking by other users, and your local modifications may thus be undone. That's why ASCET-SCM will issue a warning message when you unlock locally modified items or configurations. To preserve your modifications under version control, select Commit or Commit Configuration. See also Locking and Unlocking. |
Q | I want to edit an item in ASCET and save it as a new version, even though the SCM |
A | Proceed as follows:
|
See also