Enabling Concurrent File Editing

The personal option named Use Non-Exclusive Locks In Integrations affects how files are locked when accessed from application integrations such as Visual Studio. If you select this option, locking a file (for example, as part of a check-out operation) creates a non-exclusive lock rather than an exclusive lock.

With an exclusive lock, only the person who has the file locked can check in the file. With a non-exclusive lock, others can check in the file. Exclusive locks are the safest, but non-exclusive locks are often preferred because text files can be easily merged using File Compare/Merge. Using non-exclusive locks allows more than one person to edit a file at one time. If team members are not editing the same lines of the file, the merged file usually has no conflicts.

If you are using an application integration for your development environment, for example, the integration with Visual Studio, you cannot check in files from the development environment if both the Require Exclusive Lock When Files Are Checked In check box in the Project Properties dialog box, (Options tab) and the Use Non-exclusive Locks In Integrations check box in the Personal Options dialog box (Files tab) are checked. The administrator usually determines the setting of the Require Exclusive Lock When Files Are Checked In check box. However, personal options are set by you for your workstation.

To control file locking from application integrations, do the following:

  1. Choose Tools > Personal Options to open the Personal Options dialog box.
  2. Click Files.
  3. Check Use Non-exclusive Locks In Integrations.
  4. Click OK.

Note: If you have selected Use Non-exclusive Locks In Integrations and experience check-in problems, try clearing the check box. You may want to talk to your administrator about the setting for the Require Exclusive Lock When Files Are Checked In check box.