I have Visual SVN server running on a Windows machine. I am using the VisualSVN client that integrates into Visual Studio. Previously, we used Visual SourceSafe, which had the lock-modify-unlock versioning model. Despite the drawbacks of this model, it is what we are used to, and we want identical behavior from Subversion. In short, we do not trust the merging.
I have done the following...
- Enabled auto-props in [miscellany] section of config:
enable-auto-props = yes
- Added entry to [auto-props] to force needs-lock on all files:
* = svn:needs-lock=*
- Disable no-unlock to automatically unlock file on commit:
no-unlock = false
- Changed TortoiseSVN settings to not show the lock dialog when locking files
- Changed TortoiseSVN to auto-close dialogs if no errors.
And I have the following issues...
- When I revert my changes, the lock is not released. It should be. Is there any way I can force it to unlock when I revert?
- Edit: fixed! Everytime I begin to make a change, it automatically gets a lock, but it presents me with a dialog saying "Lock Finished!". This dialog only gets in the way. It would be nice to be able to assume that the lock was completed successfully. Is there a way to hide this dialog, and only display it if an error occurs.
How can I resolve these issues? I really don't want to hear a sales pitch on why we should use copy-modify-merge, please just help me resolve the issues.